I'm currently the primary administrator for JIRA in my organization, but we plan to bring several more people into this role in the coming months. We also have a handful of people who have administration rights, but don't do much more than configure things for their specific projects. However, I'm already finding JIRA's administration screens to be extremely hard to use. They're just so cluttered. I have nearly a hundred custom fields, 40 or so screens, 10-15 workflows, etc, and the problem is just going to get worse when we roll JIRA out to the rest of the organization for use as their work tracking tool.
So, my question is this: does anyone have any suggestions or guidelines that they follow to keep the administration sections from becoming an absolute nightmare? From my perspective, it would be great to have something like folders or tags for screens, custom fields, etc so that I could group things together. However, as that doesn't exist today, how do you manage?
It is a very generic question due to which the responses are delayed, I guess. Some rules could be
And probaly you need to figure the a set of rules as per your project context in the company, and make all the admins stick to it.
Thanks Renjith. I guess I was doing it "right" already - I name virtually everything I can with the project name included (except custom fields of course). It seems like folders would be a helpful enhancement to some parts of the administration screens. I can understand that you might not want that for custom fields, as many users might create the same field, because they didn't look in all the folders. However, for something like workflows, I'd love to be able to put each department's workflows into a folder for them.
Anyway, I'll look into adding that as an enhancement, and thanks for your feedback!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
2 votes, but only 11 views and no answers! Someone must have solved this somehow...
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.