Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×When creating a bug the required fields do not have an asterisk beside them in a specific case.
It is when the bug is created in the pop-up screen and bug is the default type of issue. If the window opens up with the story issue type pre-selected and we change it to bug the asterisks are beside the required fields.
Anybody else have this issue as well? Any ideas why this is happening?
It was because I had to make them mandatory in the behaviors plugin because I had a check on their value through behaviors.
They were already mandatory in the schema but apparently the behaviors plugin some how over rides the star.
I would recommend to use the Mandatory Field Validator of Add-On "Workflow Essentials for JIRA". See: https://marketplace.atlassian.com/plugins/de.codecentric.jira.wes/server/overview
This plugin not only shows a customized error message but also displays the asterisk next to the mandatory field.
Best regards,
Joerg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One question, are the fields mandatory by design (field configuration) or do you use the JIRA misc workflow extension or the behaviors add-on to make the filed required?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried different browsers?
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.