Hi,
I am trying to make a JIRA bug filing template. Where on the create issue screen I have a custom field which has pre-filled text into it (added using context) into the field. Where I will give sub-heading for information I want someone to enter.
This is a mandatory field.
Issue:
JIRA treats a pre-filled custom field as text, and is letting me create an issue without actually entering information in the mandatory field.
I researched and found that I can add a validator in the workflow. I have tried adding a validator.
That: "Details" CF "should be modified during the transition." from create -> to do state.
I have published this new workflow. Tried creating an issue. It is still treating the details field as text and not giving me an error while creating a bug that a mandatory CF has not been filled.
Is there a solution to this?
Did you try using Jira Automation to flag issues that were created with the default placeholder still in place? I'm also leaving a link to a Marketplace add-on, developed by the company I work for, that could be useful if you're interested. With Issue Templates for Jira , instead of manually putting default text into a custom field, you can design structured templates, pre-fill fields properly, and require users to update fields if necessary.
Hi Sana - Welcome to the Atlassian Community!
Not sure I am completely following you, but if you could add screenshots that will help.
But, if I understand, the Details field is pre-filled with a value? If so then the validator sees that the field is not empty and lets you create an issue. The field will need to be empty, or you need to use the Field has been modified Validator to ensure that the user changes the value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.