I'm trying to set up a JIRA project where a specific field (custom comment field) is required when closing a ticket prematurely (ie - not going through the full deployment process). Here's my problem:
I'm hoping I'm just going about this the wrong way, but is there not a way to achieve this?
Thanks in advance.
cc: @Enzo Licata
If you set a field as mandatory in the field configuration, then it is mandatory for the issue type.
The screens have nothing to say about making fields mandatory, all they are is a list of fields to show the user.
You need to look at the workflow to do this - make the field optional again, so you can create issues, then look at the "premature close" transition in the workflow. Add a "validator" which checks for "custom comment field is not empty" and that will force users to enter it when they try to use the transition. You will need to install an add-on to do this, but the JIRA Suite Utilities is free (And pre-installed on Cloud)
Making a field Required in the "Field Configuration" will only required it when it was being presented in the screen (like Create/Edit screen) then JIRA will not allow you to proceed if that field does not have a value.
So, what do you want to do here is make a certain field available only to a certain transition (like Close). To do this, create a workflow "Validator" in the close transition
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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