Dependencies - Possible to block start working on Issue A until Issue B isn't already done?

[Toni Richter]

Hello,
the question describes the problem.
It is possible to configure the dependencies between issues so that isn't possible to start working on issue A until issue B already be done.


I've didn't found any solution to solve the problem.
Any ideas? Maybe with another Workflow configuration?

Thanks!

---
Product Plan: Free
Role: Admin
 

[Niranjan · Accepted solution]

Hi @Toni Richter ,

You can add a workflow validator to check the status of the linked issue before transitioning the issue. There are couple of plugins that can help you with this. JSU and JWME plugin

• Linked Status (JSU) Verifies that all linked issues have a certain status.- Verifies that all linked issues have a certain status.
• Related Issues Status Validator (JMWE app) - Validates that related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.) are in a specified status.

If you are good with groovy scripting you can also try script runner for JIRA.

[Toni Richter]

Thank you @Niranjan 
I will try it ;)

It doesn't matter but is there no other option to solve this?  Without monthly payments!?
Probably I'm going to use more than this one script but at the moment I've only this use case.