How to create a field and make it mandatory only when assigning an issue to a specific step

[sai-leung_lee]

So we are able to create issues in JIRA and move them from one state to another (eg from  "In Progress" to Awaiting Test to "In Test" etc...).

As the issue progresses from one state to another you must add certain bits of information, eg Due Date? etc...  All good.

My problem is that I've taken over this system and have been asked to add a field and make it mandatory only when an issue moves to "Awaiting Test".  Call this field "Impact".  The team has been told that when their issues are being assigned to "Awaiting Testing" that "Impact" is mandatory and they must complete this field, and supply further information...

This field "Impact" can apply to any project and any issue type that has the step "Awaiting Test".

So what have I done so far to try and resolve this problem?

Under a particular project, I've clicked Project Settings, then selected Fields, then Actions > Edit Fields, clicked on the field configuration and for "Impact" assigned it to a screen:

This works when I move an issue to "Awaiting Test":

and "Impact" appears and is mandatory as expected

However, the problem is that when other issues are created, JIRA is now saying that "Impact" is mandatory, but "Impact" doesn't appear anywhere on the form???!!!:

and thus I have to go back to the Issues View Field Configuration screen and mark the field as Optional (and not Required).

[Karan Sachdev · Accepted solution]

Hello,

You have made the field mandatory by navigating to the field configuration, which is one of the correct ways to make the field mandatory, but is not applicable for your use case. Because your field configuration is shared with 82 projects, this change will apply to all those projects.

Since you want to make the Impact field mandatory when the issue moves to the Awaiting Test status, the correct method would be to use the workflow validators. This way, you can limit your change to the desired project and issue type, and enforce it at the required status transition only.

The workflow configuration steps from the below article should help:

Making a field mandatory

You can test this approach on a test project and workflow, then implement the changes in your project. Also, you can revert the changes made to the field configuration.

Thanks,

Karan

[sai-leung_lee]

Thank you Karan, your answer ties into this article which provided the solution: 

https://community.atlassian.com/t5/Jira-Service-Management/Required-field-on-one-screen-only/qaq-p/859728

[Klaudia Schön_Deviniti_]

Hi @sai-leung_lee

From the configuration perspective, the field, even if not added to the screen, must be filled if it's globally marked as required and assigned to the specific field configuration.

For this purpose, a better option is using validators or 3rd party apps. From my side, I'd like to encourage you to try a Dynamic Forms for Jira https://marketplace.atlassian.com/apps/1210820/dynamic-forms-for-jira?hosting=cloud&tab=overview which allow you to achieve the use case you have. Thanks to this application, you may define the conditions and decide when exactly the field will be mandatory, or not. 

I strongly encourage you to schedule a free overview with our team using our Calendly: https://calendly.com/deviniti 

Kind regards,
Klaudia from Deviniti