Am using automation to create an issue on transition.
Am looking for a way to prevent the issue from being created if an issue of the same type exists within the epic that is being transitioned.
For example, I have the following workflow:
Initially when I move from Open to Requirements, I want to automatically create a requirements issue type.
On the other hand if I move back from Development to Requirements, I want to open the existing requirements issue, instead of creating a new requirements issue.
Thank you very much in advance.
You should be able to do this with entity properties, so when you transition the epic, you can mark with a property saying that the issue has been created, preceding that you check the non-existence of that property. Here is an example:
Let me know if that will work for you.
Thank you for your help.
I went about this in a different way as I got stuck if a user manually deleted the issue (and i did not want to add another automation to clear the hasissueCreated property.
My solution was to create two automations.
1. Create issue if the issue does not exist (using the related issue condition).
2. Reopen issue if the issue does exist (using the related issue condition).
Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk! We’d love to hear your thoughts on the pros and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs