I am trying to create an easy flow for hiring managers to review job description on Confluence and then have the ability to click a smart button that auto-fills the 'Open a Job' request on JSM. It would be amazing if there was a way that I could parse the content of the job description on the page to auto-fill the fields on the work item.
Does anyone have suggestions to make this work? Maybe other ideas around this?
Hi @Cat Tinsley 👋🏻
First of all, welcome to community! ✨
To answer your question, it looks like to parse content from a Confluence page into Jira fields, you can use built-in tools like Atlassian Rovo AI, automation rules with Send web request action.
Option 1: JSM Automation via Webhook
{{page.body}}Option 2: Atlassian Rovo AI
If your organization uses Atlassian Intelligence/Rovo, you can use the built-in AI agents.
Set up a Rovo Agent on your job description page space. The manager can prompt the agent, "Create a job request ticket for this role." The agent will automatically extract the requirements, summary, and location from the Confluence page and map them directly into a JSM ticket.
You can also refer this Tutorial for more details.
I hope this helps & resolves your issue. 🙂
Thanks,
Anwesha
Hi @Cat Tinsley ,
I would probably also suggest going with/trying Rovo agents. You can probably follow this article for it: Create service requests with Rovo agents
Also, related to agents, there's this request: ROVO-299: Allow admins to configure specific recommended agents for users to access in Rovo Chat > with that, you could maybe recommend that agent when a user opens a Rovo Chat.
Automation is also a viable option, but might not be that flexible...
I've also seen cases where users would use pre-filling via URL parameters 👀
Basically, something like this:
How it works: You append specific parameters to your JSM request form URL.
https://your-site.atlassian.net/servicedesk/customer/portal/1/create/10?summary=New+Job+Opening&description=Review+attached+JD
This is probably the least flexible solution, but it's fairly simple to build and use. But it's not parsing traditionally, and actually 'understanding' the context behind the page and the content.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.