You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
This workaround is meant to help projects where it is necessary to assign a new issue/request directly to a specific agent to better organize the queue management.
For a such scenario, I used ProForma with Automation For Jira(A4J). Also, I used as an example a form related to an IT - Change request, where the customer will select in a radio buttons fields the option of IT change. For which option chose the new request will auto-assign to a specific agent. This method can be used for other purposes (eg. issues with approvers).
Important related documentation:
Building Forms in ProForma
Working with Service Projects
Working with Software & Business Projects
ProForma & A4J
How AFJ works
Advanced field editing - JSON
Note: Because ProForma updates the issue and linked fields with a milliseconds delay after the issue is created, when more information a form has, more "Re-fetch issue data" actions will be necessary to add so that this delay is rewarded and the automation rule can get the form values.
Note: To find the custom field ID please take a look at this documentation. Also, to get the ProForma proprieties you can access it using this URL below: