When transitioning from one state to another (For example from "In Progress" to "Resolved"), I have a "Resolve Issue" screen. I would like one of the custom fields on that screen to be required.
My choices for implementation appear to be these two choices:
I don't like #1 because the user will not necessarily understand why the "Resolve" transition button does not appear for them. #2 is OK, but then the users are asking why there is no red asterisk next to those required fields when they enter the screen. I don't want to make them required in the field scheme since they are not required until this point in the workflow.
Any other possible ways to implement this?
There are add-ons that allow you to make the fields required using approach #2 and have a red asterisk.
You can do that with:
I would recommend Script Runner as it allows virtually any kind of customisations in your JIRA instance
I don't believe any of the plug-ins that will make a field required on a transition puts the asterisk next to the field. You can get around it by including the asterisk in the field name if it really bothers your users. The lira-suite-utilities plug-in will pop a message it is required if they didn't fill it in when clicking to complete the transition. I've never had much push back from the users as long as they are told in training about the behavior.
I'm afraid you'd have to code an add-on to get something like that. Validators can't have an asterisk in the transition screen, since the actual call to the transition hasn't happened yet, therefore the screen cannot "know" that the transition is valid or not.
#2 is really your best option there. Although there's no red asterisk, when you try to submit the form there will be a customizable red message. Users will get used to it soon enough in my experience.
I would recommend to use the Mandatory Field Validator of our Add-On "Workflow Essentials for JIRA". See: https://marketplace.atlassian.com/plugins/de.codecentric.jira.wes/server/overview
Otherwise you could use "Script Runner" and "JIRA Suites Utilities" which are bit more complicated to setup.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs