I have a required field (Account) that does not work like a required field unless it is actually opened. I want to make the field required anytime a user attempts to transition an issue.
I see articles like this but it doesn't look up-to-date. I am using the Jira Simplified Workflow on Jira Cloud.
Is this possible?
Hello @Jesse Maxwell
In order to accomplish that you will have to switch from using the Simplified Workflow to using a customized workflow. As per this article, the design of a Simplified Workflow is intended to allow issues to move freely from one status to another.
After switching to use a customized workflow you can add a screen to the specific transition to display the field, and add a Validator to the transition to require the field to be non-empty.
Simplified Workflows don't work that way - they explicitly remove the popups/screens on transitions - so it's a one-or-the-other scenario. You'll have to use a regular workfow (not-simplified) and then then validators or post-functions will work.
You can read about simplified workflows here, including a sort-of-explanation of why it won't work the way you want.
https://support.atlassian.com/jira-software-cloud/docs/use-the-simplified-workflow/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can actually modify a simplified workflow and add screens and validators.
But you could easily lose some or all of your customisations if one of your board admins decides to change the workflow. So I would net recommend modifying a simplified workflow. As Chris says, de-simplify first, then edit a standard workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.