How to add Mandatory field when close an issue ?

[CYH]

Hi, we have 4 issue type when we create jira ticket .
They are Task, Epic, Story, Incident.
When we create jira ticket with any one of issue type, we only need to fill, for example, Summary , Assignee, Due Date, Description.
Now we need to function that
when we close an INCIDENT Jira ticket, we have to fill [Root cause] (this is a new field which doesn't show on the create jira ticket page) otherwise it can't be close.
How to do this?

I try to edit the workflow to add onemore step after Done. But as the the workflow scheme is shared by other 5 projects and i doon't want them to be affected. Could you help to do this? 

[Rilwan Ahmed]

Hi @CYH ,

We have done it using "Teamlead ToolKit - Boost Workflows & JQL" or JSU Automation Suite for Jira Workflows  free plugin. These plugin provides "Field Required Validator" which you can add it on the transition to Close (example: Inprogress to close).

Follow below steps to achive this.

1. Go to Admin --> issues --> Screen 
   Create a screen and add "Root cause" field to it
2. Go to required Workflow, edit the transition to Close and in Transition View, select newly created screen
3. Add validator "Field Required Validator" and select root cause in "Select the Custom Field to be validated for empty value".
4. Publish the workflow. 

Please note: If your workflow is shared with other projects/issue types. this change will be applied to them as well. 
Workaround: Copy the workflow and workflow scheme, modify workflow as mentioned above. Add the copied workflow to the copied scheme and assign it to the only required project. 

[CYH]

HI Rilwan, Thank you so much for your detail guide. 

I follow the steps above, but all issue type are required to fill [Root Cause] now.  

How to make it only work on "Incident" type?

could you help again?

[Rilwan Ahmed]

Hi @CYH 

Seems you are using same workflow for all Ticket types in the project. 
Go to Project settings --> Workflows and check what workflow is mapped to "Incident" ticket type and other  ticket type.
Please share the screenshot of this page for better understanding. 

[Rilwan Ahmed]

Hi @CYH 
Please accept the answer if the solution worked for you. 

[CYH]

Thank you. @Rilwan Ahmed 

If i understand you correctly, you are saying that we need to ensure that the project we want to change should have a  workflow that doesn't share with other projects, otherwise we copy the workflow and workflow scheme and re associate with THE projects. 

[Rilwan Ahmed]

Yes. 

[Somesh Sahoo]

https://youtu.be/W3vhZJkJ52A

Please see this video for Solution.