How to write a automation rule so that when blocked issue is done then the linked issue can be done

[Eslam Abdelrady]

I need to make an automation rule that only allows the blocked issue to be in Done status first before the linked issue is Done:

For example: Issue A can't be solved (Done status) unless Issue B is solved, these are sub-tasks linked to each other according to my workflow

[Ubaroz]

@Trudy Claspill apologies for resurrecting this, but this is the only place where I found a reference to what I am looking for.

What you wrote above is exactly what I am trying to achieve:

"If not, with an Automation rule you would be able to detect that Issue A was in a Done status while issue B was not, and you could get a notification about that"

My needed automation logic:

IF

[Work item A] is transitioned to "Done"

AND

[Work item A] has a linked [work item B] blocking it (linked issue: "blocks")

AND

[Work item B] is NOT "Done"

Then

Comment on [Work item A] ("Attention!
This work item is blocked by another work item and should not be marked as "Done" until the blocking work item is completed first.")

It seems quite simple to do, but I can't seem to find the proper way to make it work.

Any help is appreciated, thank you

Ubaroz

[Evie Z_]

@Ubaroz 

This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .

Thank you for your understanding!

[Trudy Claspill]

Hello @Eslam Abdelrady 

Welcome to the Atlassian community.

An Automation Rule cannot prevent an issue from having its status changed to Done. Restricting status transitions can be done only through customization of the workflow for that issue type in its respective project.

And native Jira functionality does not provide an option to implement the conditions you want in a workflow.

Are you willing to consider getting a third party app to meet your requirement of preventing the status change?

If not, with an Automation rule you would be able to detect that Issue A was in a Done status while issue B was not, and you could get a notification about that, but you could not prevent that scenario.

Note also that there are limits to the number of rule executions that are allowed per month. You will need to consider all the rules executing in your instance and determine if you usage is low enough that you could add another rule for this.

https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

[Eslam Abdelrady]

Thank you for your reply @Trudy Claspill 

I think I should take a look at the third-party apps to meet my requirements would you recommend an app for me please I would appreciate your help in this matter

[Trudy Claspill]

You might be able to do this using the Adaptavist ScriptRunner app.

If provides various extensions for customizing workflows, including adding Conditions based on Jira Expressions.

https://docs.adaptavist.com/sr4jc/latest/features/workflow-extensions/conditions

If you can create an appropriate condition, then you could block the transition. I have not tried to accomplish your specific goal, so I can't provide the solution details. 

It looks like Jira Workflow Extensions also has a function for this:

https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323193/Linked+Issues+Status+Condition