The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Block transition of a task based on the status of a task in another project

Michael Maram
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 1, 2024

I want to block transition of a task to 'In Test' unless all of the linked dependent tasks in a different repo have a particular status.

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Maciej Dudziak _Forgappify_
Atlassian Partner
August 1, 2024

Hi @Michael Maram

If you are open to using apps and looking for a ready-to-use solution. We've developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira app. With a wizard-like UI, you can choose relations from: sub-tasks, parent issues, epic children, and linked issues. Additionally, you can filter relations by issue types and select criteria based on status category and status.

I hope it will help.

Cheers

0 votes
Hans Polder
Community Champion
August 1, 2024

@Michael Maram , 

You could solve this in numerous ways.

  1. There will likely be plenty of apps in the Marketplace (that might be paid for) that would allow you to do this out of the box. If you want a neat solution that can be re-used and applied in different parts of your system (in multiple workflows), you might want to check that out.
  2. Native Jira doesn't support a condition on a transition that checks for 'linked dependent tasks'. However, what you could do is a variation of the 'potential solution' I've described below.

 

Quick & dirty solution

1. Create a custom field but don't make it visible on the Edit Screen, but not View or Create Screen of the issue type you're working on.

2. Use Jira Automation (a global rule that can only be managed by admins) to trigger on 'Task closed > check parent > for parent, check if all linked childs/tickets are matching a certain JQL (as in "all are closed") > then fill a certain value in the created custom field.

3. THen, in the workflow for the ticket that must not go to 'In Test' if the linked tickets are not closed, you can add a condition for 'Value Field', referring to the custom field that you are updating via Automation to be a certain value. If that value is met, then the condition will allow the transition to be visible.

 

It's not pretty, but it should work. Again, if you need to do this more often, definitely consider Marketplace apps for this :)

Michael Maram
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 4, 2024

Thanks @Hans Polder - I am trying to stay away from a paid marketplace option which can be quite expensive. I will look at your alternate solution. 

Like Hans Polder likes this
Hans Polder
Community Champion
August 4, 2024

Let me know if it works out! :)

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events