I want to setup JIRA automation that ONLY sends out a notification when all dependencies on an issue are met. How can I do that?
You'll want something like this:
What's happening here is that as issues move to your resolved status (DONE in my example), it navigates to any issues it is blocking. Next, it verifies that all blockers are resolved. If this matches, it sends an email.
Mark, thank you for this. See my current rule setup below:
How can I edit this current rule setup to include the missing part which is the branch that you have (for linked issues, types blocks). or do I need to construct the rule in a different way to include that missing component?
Thank you for your help.
For clarity, are you looking to have it send two notifications?
If this is the case, it looks like you already have the branch so you can just add the linked issue condition (you'll want to change it to the other half of your "Depended on by" link type) and the second send email action.
Mark, I apologize but I don't 100% follow.
Essentially we need to keep "is depended on by" in place, because of the following use case:
team A should be notified when dependency on team B is completed. But do not notify team B when dependency on Team A is completed.
given above, we just need to modify the rule so that all the dependencies must be completed before team A is notified.
Hope this was not too confusing.
If possible I'd like to keep this all as part of one rule.
I understand the ask. I just need to understand the link type. For example, there are two types of link types:
Is Depended On By is not a native link type, so I'm just trying to get a sense of whether it is configured like 1 or 2 above. My example assumed hierarchal so if yours is more of a simple reference we need to make a slight tweak to things.
If it's hierarchal then the rule I proposed should work, but there should be a different link type the other side. Perhaps you can share screenshots of two issues that are linked to each other. I just need to see what the link type is called on each side of the link. If it's the same, then you're dealing with a referential link
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event