I have an automated Rule that create tickets based on components stamped in the parent ticket. I would like in the tickets that are automatically created for their summary to include the Key and summary as well as a set prefix of the parent ticket that triggered them to be created.
Hi @Salli El Ramadi -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
Would you please explain the problem you are trying to solve? That is, why do this?
Issues displayed in Jira already show their parent's key and / or summary in various ways, such as the breadcrumbs. Adding the parent information into the children's summary will create a potential synchronization problem to manage.
Kind regards,
Bill
@Bill Sheboy - I'd like to piggyback off of this.
I have a setup where a ticket is raised in Project A, and it immediately creates a linked ticket in Project B. I need the ticket number/key to be added to the linked ticket in Project B in a custom field because Project B is set up with an API to Azure DevOps. I can't for the life of me figure out how to get the originating ticket number (from Project A) to flow to ADO.
This is needed for when someone with portal only access has to discuss the original ticket with their account manager.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Although it is great to add to existing suggestions, your question seems a variation of this one. And so I recommend creating a new question next time; that will help focus the conversation on one question at a time to get to solutions faster. Thanks!
For your need, and without seeing your rule details, please try using this to get the key from the triggering issue for the create issue action:
{{triggerIssue.key}}
If that does not help, please create that new question, posting images of your complete rule, the actions, and the audit log details. Then put the link to it here to redirect readers.
Kind regards,
Bill
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.