Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,883
Community Members
 
Community Events
168
Community Groups

Item Transition Check

hello please
It is possible to create a check, where it will only be transacted if all linked items are in a certain status.

Thanks!

1 answer

1 accepted

3 votes
Answer accepted

Hello @Silvio 

Are the linked items linked using the generic issue linking functionality or are the linked items Sub-tasks under a parent issue?

Generally you use Workflow Transition Conditions to determine if a change from one status to another is allowed. Workflow Transition Conditions hide the new status if the conditions are not met. Validators allow you to try the transition, but will block it if the conditions specified in the Validator are not met. For more information refer to

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

Some third party apps, like Adapativist Scriptrunner, will extend the workflow features to allow you to make more sophisticated Conditions and Validators.

Thanks for the quick response!

The use case would be:

Allow Epic to transact to the next status only if all related items are complete.

As per the documentation I referenced, there is not a built-in workflow Condition for checking the status of Child issues when trying to change the status of an Epic. There is also not a built-in Validator option for that.

There are a couple of options available to you.

1. Look for a third party app that extends the Workflow capabilities to give you a way to build a Condition or Validator for this.

2. Create a custom field in you Epics to track if the condition is currently met. Use an Automation Rule to update that field. Then, depending on the type of Custom field you created, use a Value Field condition or a Compare Custom Number Field condition to block the transition. This adjustment would need to be made on a workflow that applies only to the Epic type issues. This applies to Company Managed projects. Guidance for a Team Managed project would be slightly different. 

Thanks for the support!

Hug!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,085 views 18 32
Read article

Atlassian Community Events