Set Feature, Story, Sub-task as ReadOnly When Portfolio Epic Moved to Next Status?

[Digvijay Singh Gehlot]

Hi Community,

I have 4 level hierarchy : Portfolio Epic > Feature > Task > Subtask in a project.

My use-case is:

When Portfolio Epic moves from In Progrss to Close status, then all it's linked children should be set as ReadOnly irrespective to Child's status.

For example:

EPIC-1000 has it's child as FEATURE-2000 

> FEATURE-2000 has it's child as TASK-3000

> TASK-3000 has it's Subtask as SUB-4000

If EPIC-1000 moves from In Progress to Closed status, then all it's Children (Features), Grand Children (Tasks) and Great Grand Children (Subtasks) should be set as ReadOnly irrespective to Child's status.

Please assist for the above if it is possible via Jira Automation Rule, scriptrunner behviors, jmwe app, etc.

Thanks 

[Trudy Claspill]

Hello @Digvijay Singh Gehlot 

What problem are you trying to solve by making the descendant issues read-only?

What would you expect to happen if the Portfolio Epic status changed again to something other than Closed?

Is it a requirement that this be accomplished without changing the status of the descendant issues?

If not, then one option would be to add a status (i.e. named Read-only) to the workflow of each of those item types. Set the Properties for that status so that the issues become read-only. Create Automation rules to address moving the descendant items to that new status when the Portfolio Epic transitions.