How to restrict creation of Child Issue Before a Feature is approved

[Anshuman Ankur]

Hello Community,

We are using Cloud Enterprise version of Jira. My current workflow is set as :

EPIC -> 1st Feature gets auto created as per business requirement and then status of Feature is New. 

Scrum team can then add child issues - Story, Tasks, Sub Tasks to a Feature and Transition the Feature to "Feature Ready" status.

Requirements:

1. I want to introduce a new status in Feature workflow as "Waiting for Approval" for any subsequent Features being created under the EPIC. The automation for 1st Feature creation should still work. 

2. The approval can be provided only by a certain role which I can configure in Users. This I know how to do. 

3. When the Feature is in "Waiting for Approval" status. I want to restrict the ability of users to be able to create any child issues - stories, tasks etc. 

Please suggest your ideas on how to achieve this. Or if any similar question is already answered. 

Thanks,

Anshuman 

[Marc - Devoteam · Accepted solution]

Hi @Anshuman Ankur 

Welcome to the community.

The "Create Issues" permission applies to all issue types, so it's not possible to limit users to create certain types of issues through the permission scheme.

Based on validation on a workflow, used by an issue type, you can set users of groups creation based on a validator.

[Anshuman Ankur]

Thank you Marc. 

The "Create Issues" permission applies to all issue types, so it's not possible to limit users to create certain types of issues through the permission scheme.

Yes I want to restrict any issue type creation as long as the Feature is in "Waiting for Approval" state. Once the validator approves it- it should follow the regular workflow. 

This is where I am struggling. 

[Marc - Devoteam]

HI @Anshuman Ankur 

This is not possible.

Create permissions are based on the permission scheme and relate to all issue types used in the project.

[Anshuman Ankur]

Okay, So if I understand correctly create permission is not related to the status of the Issue type, it is global. I was referring to another thread - 

https://community.atlassian.com/forums/Jira-questions/How-do-I-prevent-User-Stories-from-being-added-to-a-closed-Epic/qaq-p/926928#U3010505 

So if it is possible to restrict on the page view for a Closed/Done Epic, can this be used for a new status like "Waiting for Approval"? 

[Marc - Devoteam]

Hi @Anshuman Ankur 

These workflow properties are also for each issue using the workflow and applies to the issue in a certain status.

I won't prevent creating issues in a project, and won't prevent the option to add-sub-tasks or link issues to an Epic issue type.

It can hide the add child option to an Epic issues type, that's it for your case.

[Maciej Dudziak _Forgappify_]

Hi @Anshuman Ankur

Do I understand correctly, that you have a custom hierarchy:

Epic -> Feature -> Story / Tasks 

Therefore those applies:

1. a parent of the Feature is Epic, 

2. a parent of Story/Task is a Feature

3. There can be several Features under 1 Epic, and you want to block creation of  subsequent Features until previous is moved our of status = Waiting for Approval ?

Cheers

[Anshuman Ankur]

Helllo Maciej,

Points 1 and 2 are correct, For point 3 What I want to do it not allow any Story/Task to be created until the Feature is moved out of status = Waiting for Approval.

[Maciej Dudziak _Forgappify_]

It would be possible with Jira expression-based validator, e.g.:

issue.parent != null
&& issue.parent.issueType.id == 10006 
&& ![10011].includes(issue.parent.status.id) 

Basically, you could create a Validator on Create transition, which would prevent child issues to be created when a parent is of issue type = Feature and is in status = "Waiting for Approval";

but, because of a bug: https://jira.atlassian.com/browse/JRACLOUD-85039, it won't work unfortunately

[Marc - Devoteam]

Hi @Maciej Dudziak _Forgappify_ 

This would require a 3rd party app right, like JWT, or can this be done ootb?

[Maciej Dudziak _Forgappify_]

Hi @Marc - Devoteam 

Yes, it would require 3rd party app