Item Transition Check

Silvio September 16, 2022

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
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 16, 2022

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.

Silvio September 16, 2022

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.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 16, 2022

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. 

Silvio September 16, 2022

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
AUG Leaders

Atlassian Community Events