It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
We have a custom team field and have it set to required. The option "None" is appearing as the default and is counting as populating. Ticket creators are not forced to identify which team the ticket belongs to.
Anyone know how to work around this? I know how to change the default value, but that will not solve the challenge of people not assigning a team to new tickets. Looking for a way to have the value as Empty (or not populated) to force ticket creators to pay attention to that field
It is not a script. A simple "Validator" called "Field has been modified Validator" provided by the JIRA Misc Workflow Extensions add-on.
It sounds like you have an option of "none" on the list of options - that's why the "mandatory" flag is picking it up as being filled. If you reconfigure the custom field, you should be able to remove the default, and then disable the "none" option. JIRA will then present the user with "none", still, but it will mean "nothing selected". Then the mandatory flag will kick in if the user doesn't select something else.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.