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
So we have set a custom issue view for our "Submit a request or incident" request type
When i manually create an issue and select the above request type, the issue view is as it should be, see attached 1st picture
2nd picture is what the ticket looks like when jira automation rule creates the ticket under the same request type
you can also see on the 2nd picture it has a blank request type field which if you change manually it will then populate after a refresh the correct view
pic 3 shows the automation rule
What leads you to believe the automation rule action is using the incorrect issue view?
For a question like this, please also post the audit log details showing the rule execution. That will provide additional context for the rule execution.
Thanks for describing the symptom.
The likely cause of this is the Issue Created trigger can fire so quickly that the data is not yet available to the rest of the rule. This can lead to conditions / actions / branches having missing data.
The work-around / fix for this is to always add a Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule by about a second and reload the issue data before proceeding.