Within JIRA I have created multiple projects, and within them multiple Issue Type.
Within each of the Issue type, new screens and screens schemas are created for each.
Just now I switched the "required" on for some of the fields, expecting them to to mandatory for screen that have them in its configuration.
But what's happening now is the mandatory fields I have switched on, they are affecting other Issue type. Meaning the particular fields is not even on the create issue screen, yet when we click on "Create" button, it shows a error message "XXX is not populated"
As mentioned in my second sentence, I have created seperate screens and screen schema, so I really am no expecting them to affect another other screen. Why is it still happening?
Note: I did create all of the custom fields in Default Field Configuration , Is this where I'm going wrong?
If I have to seperate the field configuration for each of the screen, and each of the screen schema, how do I do that?
Screens have nothing to do with mandatory fields, they are just a list of fields that will appear when you try to do things with an issue.
The field configuration, where you make a field mandatory, is the important thing. If you have a field configuration that is used for every issue type in every project, then making a field mandatory in that field configuration will make it mandatory in every project and issue type.
You need to have different field configurations by project and issue type.
Thanks Nic, you are correct. Purhaps I knew all along I have to create different field configurations for each project and issue type. I just didn't want to do it because it's so time consuming.
Why is JIRA so hard and time consuming to administer? Everything has to be done 3 or 4 times, I have to navigate to multiple pages just to do one thing?
(No need to answer, they are rhetorical questions, I'm just having a whinge)
Well, I know it's a rhetorical question, but I do empathise with you. The basic answer is that if you want flexibility, you end up with complexity of setup. A lot of software is far more simple to configure, but because of it's inherent simplicity, can't be used for clever stuff. Some goes to the other end of the scale and is so complex, you can't even get to the flexibility because it's just too hard. Jira is somewhere in the middle. But there are things I'd like to improve, especially around field configurations.
One minor piece of advice though - don't create schemes for *every* project. Try to create a standard way of approaching a type of project, and then reuse as much as possible. For example, the last organisation before I went for a bit more flexibility in my career used Jira for incident tracking, monolithic development, several Agile variations, a risk register and a few other things I won't bore you with. The dev projects are the best example - we had 8 distinct schemes (actually 3, 3, 2 - split by business unit), and 500 projects using the 8 schemes.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs