Hi all,
Is there a way to make a custom field mandatory only when the issue is moved to a certain status?
Regards,
Samuel Srun.
Hi Samuel,
If you have an add-on like JWME or ScriptRunner or JSU - then you an add a validator to the workflow for the transition to the appropriate status for Required Field.
Hi Samuel,
I am part of the Decadis Support team and i would like to recommend you our app Jira Workflow Toolbox (Server/Data Center) .
In particular, in the transition to the corresponding status, the validator Fields required or changed checks if fields are set/empty or have/haven't changed on the transition screen.
If you need any assistance with our application, I encourage you to create a ticket on our support portal.
Best regards,
Nacho
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This would be another good tool to use. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Samuel James ,
Yes, it is possible to do this natively in Jira.
Let's say you want a text box called "The reason" to be filled whenever an issue is transitioned to the "Impediment" status. I'll provide the exact steps for the scenario above, but you can adapt them to fit your needs:
This will ensure that when an issue is transitioned to the "Impediment" status, a screen will appear prompting the user to fill out the "The reason" field.
I hope this helps! Feel free to reach out if you have any questions or encounter any issues—I'll do my best to assist!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You realize that the field must be populated at the point you create the issue if it is in the Field Configuration, right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk
Thanks for pointing out this issue. Indeed, it needs to be populated when the field is set to required.
The default value of "N/A" or "TBD" can be set for "The Reason" custom field upon creation.
An automation can then clear that field after the "Issue Created" action is triggered.
I understand that in this scenario, a more efficient approach might be to use a third-party marketplace app, but I also believe in the true power of Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can’t clear out the value of a required field. Have you actually tried what you are suggesting and had it work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk ,
I appreciate your concern for providing the community with the most accurate information. I did indeed try before posting here. As far as I am missing something, the solution does work.
So, I recorded a quick video to demonstrate it. Please check it out and let me know what you think!
https://youtu.be/x3O-K61PCIw
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you sure set the field to Required in the Field Configuration? I did not see you fill out that field at Create.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk ,
Yes, it is required, and you can see it in the video. What happens behind the scenes is that the field has a default value set, so it is not required to fill it upon creation (it gets set automatically)
However, after the issue is created, the field is immediately cleared by an automation, leaving it blank.
Then, when the user transitions the issue to "Impediment," since it was emptied by the automation, it must be filled in to complete the transition.
I would like to remind you that this is a POC and can be adapted depending on one's needs.
I would be happy to answer any further questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the clarification that you you are setting the default value - that was not mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk,
I am glad if I was able to answer your questions. Sharing ideas and discussing the limits of Jira with such an experienced community leader was both a pleasure and a valuable learning experience for me.
I believe I mentioned in my second post:
"The default value of "N/A" or "TBD" can be set for "The Reason" custom field upon creation."
Please let me know if you didn’t receive that message, and I can resend it.
Have a nice day!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, I missed that about the default - you probably want to mention that with the creation of the field. Also, I noticed in your test that it looked like you were using Cloud - and this question is for Data Center. In this case, I think it still works as you outlined it - just be aware of those differences though. :-)
All-in-all, I think you have a good solution - well done!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.