Hi @Michael Arndt
There are two options that I can see:
- Condition: Add a condition that "In Progress" cannot be transitioned to without an Assignee
- Multiple Flows: Have multiple flows to incorporate the need.
-------------
Condition:
- A condition requires a value to be present before the transition is made.
- Conditions will "hide" the status from a user's options - so they wouldn't see the status unless they met the condition required
To set this...
- Go to Jira Settings > Issues > Workflows
- Select the appropriate workflow from the menu, and choose to "Edit"
- Select the transition to "In Progress" - and in the pop-up, select Conditions
- Press "Add Condition" in the next screen
- Utilise the condition "Value Field" - to ensure Assignee is not blank.
-------------
Multiple Flows:
If a condition isn't what you're looking for - I have seen teams use a multi-flow approach.
This is what I mean:
- There are two separate transitions to "In Progress"
- One requires Assignee to be populated. There is no screen on this option.
- The second requires Assignee to be empty - this has a screen and a validator to ensure during the transition, Assignee is entered
That way, only one of the two transitions has a screen. This is a brief overview of how to implement this:
- Go to Jira Settings > Issues > Workflows. Locate your workflow and press "Edit"
- Select the current transition to "In Progress" - and in the pop-up, select Conditions
- Add the "Vale Field" condition - to ensure Assignee is not blank.
- Next, add a second transition to "In Progress" from the previous status. It'll need a different name than your first (eg. To Progress, Progress, Start Progress, etc)
- Go to Conditions - and add a second "Value Field" condition - to ensure Assignee IS blank
- Next, go to Validators - and add the "Field Required Validator" - requiring Assignee to be set during the transition
- Finally, on the original transition pop-up press "Edit" to add the required screen when Assignee is empty
^ A few things to bear in mind:
- If you're utilising an All-to-All transition pattern, the new transition cannot also be All-to-All also.
- If utilising All-to-All, you might want to consider if statuses past "In Progress" also require a condition that Assignee needs to be populated, to stop users jumping over this validation.
- You could add further double-flows to other statuses with the same validator if necessary.
-------------
Let us know if either of these options fit your need!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.