How to make Fields mandatory on Edit screen, when we apply for In Decision status?

[Ravikanth Chinthakuntla]

Hi Team,

Is there any way to make Fields mandatory on Edit screen, when we transition the issue to In Decision status?

Scenario: 

We are looking for a behavior when we move the status from In progress to In Decision, we want four fields to be mandatory on the edit screen only when the status is In Decision.

For remaining statuses on the Edit screen the same fields to be optional and only when the status is In Decision four fields should be mandatory

Can you please help me with the behavior for this requirement

Thanks

Ravikanth

[Tessa Tuteleers]

Hi @Ravikanth Chinthakuntla , 

curious question! 

Why would you need them to be mandatory on the edit screen?
As you explain yourself, you need them to be mandatory when you transition from "In progress" to "Decision". 

In this case, you can use a transition screen with added validation that those 4 fields are required. (You would need an app for that, there are a lot of useful workflow extending apps on the marketplace).
This way, you must fill them in during the transition.
However, when you reach the "Decision" status, the field could technically be cleared again.

If you want to prevent that, you would need an app like ScriptRunner and use behaviours to make fields required on any condition (like status).
But you might have your requirements fulfilled with the much simpler validator. 

Hope this helps! 

- Tessa

[Ravikanth Chinthakuntla]

Hi Tessa ,

Thanks for the reply

As the fields were already been mandatory on the transition screen now I want to make them mandatory on the Edit screen as well by using a behavior.

Let me know if this is feasible or not. If yes please help me with the such script.

 If this requirement can be fulfilled with the much simpler validator it would be great If you can help on how to achieve with this?    

Thanks

Ravikanth     

[Tessa Tuteleers]

Hi @Ravikanth Chinthakuntla , 

if you already have the fields mandatory on the transition, the validator is already in place. 

If you still want to make sure no-one can clear the fields during that status, then a ScriptRunner behaviour is necessary. 

I can give you 2 great references from which you can create your own behaviour if you have a little scripting experience: 

• Useful code example by adaptavist of how you can conditionally make a field required
• The way to get the current status of the issue to use that as your condition

The world of behaviours is a fun one so start exploring, but be warned. Since you are on server, if you are thinking to move to Cloud in the near future, behaviours are not entirely supported (yet), so steer clear then.. 

Good luck! 

- Tessa