The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation create ticket doesnt use correct issue view

Khuram Khalil
October 13, 2023

Hi all, 

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

pic 1.PNGpic 2.PNGpic 3.PNG

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2023

Hi @Khuram Khalil 

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.

Kind regards,
Bill

Khuram Khalil
October 13, 2023

if i manually create an incident, its fine, 

 

When automation creates it, for some reason it doesn't apply the view / "Request type" field in the 2nd picture

very weird completely has me baffled 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2023

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.

Khuram Khalil
October 13, 2023

thats what i was thinking, but didnt know the term to use, thanks let me try that and ill let you know!

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events