nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create a rule to prevent 2 issues of the same epic to pass a certain column alone

Filipe Dziedicz

Is it possible to create a rule where I cannot move an isso from an epic if another issue of the same epic is not on the same column (Status)

Example: Task 1 and Task 2 are both from Epic Test.

I would like to set a rule where Task 2 cannot progress from the column QA to Waiting PO Approval without Task 1 being on QA too

Accepted answers

Kian Stack Mumo Systems

@Filipe Dziedicz is the requirement that a single issue must be in the status, or that all of them must be? I am not sure of what you are trying to do is possible or not, but I want to make sure I understand the requirements!

thanks,

Kian

All comments

Kian Stack Mumo Systems

thanks,

Kian

Filipe Dziedicz

I would like to divide the board in some way, I tried using configurations of workflow so that Not issue of the same epic should go to Waiting PO Approval without all issues of the same Epic be on QA (The last column before Waiting PO Approval)

Kian Stack Mumo Systems

@Filipe Dziedicz,

I don't think there is any way to do this easily. You could look at the JSU Plugin. This has a "linked status" validator which could potentially be used, but I think you would need to link all of the tickets in the Epic together, which might be kind of a pain to do.

Thanks,

Kian

Filipe Dziedicz

Thank you for the clarification

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud