You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I first started Administrating Jira, I inherited an older installation of the software. We have instructional documents that show screenshots from Jira 3.12! So it's been here a while and changed ownership more than a few times. There have been few agreed upon standards and little to no best practice oversight....which means I get to see some really strange things, in deep dark corners of Jira....
Today's odd find of the day gets kinda deep and goes into Field Configuration
I had a call, about a user dropping into an old project to see if they could revive it for their team or pick the pieces out to use in a new project for their new project. So they go to create a new ticket, see what fields are available, how it moves through the workflow, etc and when they try to create the ticket, the get an error about a field being required, yet the field doesn't show up on the screen!
Looking at the screen configuration for the Create screen, and sure enough, it isn't there. Just for good measure, I look at the View/Edit screen. Nope, not there either. Now, easy fix is to just add the field to the screen, have them fill it out and we can proceed. But the field wasn't suppose to be there and wasn't relevant to the project.
So here's where we get to the head scratching part. How is a field required, but doesn't have to be included on the screen?! You have me on that one, but I can tell you how to go in and clear it, so it is no longer required.
Fields can be marked Required in two ways. One way is in the workflow, you can use a validator on the transition.
That's a pretty easy thing to find and fix.
Another way, is that the field was set to Required in the Field Configuration Scheme. You can see what Field Configuration Scheme your project is using by looking at the project summary and click directly into it from the information found there.
*pro tip* Don't edit Default Configurations!
Scroll down until you find the field that has been marked Required and click on Optional. It will remove the requirement for the field, and the issue will be able to move past the Create screen.
What weird, wild or odd things have you encountered in your old installations of Atlassian products? Go ahead and share them in the comments!
Kimberly Deal _Columbus ACE_
Columbus Events Leader
18 accepted answers