Question - we have a bunch of Issue Type Screen Schemes, Screen Schemes and Screens in our JIRA instance that I would like to cleanup!
It looks like there are a lot of default schemes and screens that are the same but renamed upon creation to reflect the project they are on.
What steps should I take to verify and consolidate projects to the same screens / schemes and delete the unwanted screens, screen schemes and issue type screen schemes?
(It looks to me as if you need to go into the nitty gritty and compare screens to screens and schemes to schemes with a big computer monitor?)
In order to understand how fields, screens, schemes are used by your organization you need to understand how are they actually related to projects. Once you have an understanding then you can refactor, delete, reorganize, etc.
Without this overall view, you will not be able to confidently reorganize or delete artifacts as you might affect functionality in some of your projects.
And without cleaning your Jira artifacts you will see in time that your db size will grow as well as your Jira performance will decrease. But worse, you will have to deal with an exponential number of artifacts that might be unused or obsolete, and that will affect your decision making.
Config Insights for Jira is allowing you to visualize how each such artifacts are associated with projects. And it also gives you the option to bulk delete what artifacts you consider unused.
Thanks Petru -
Yes - it was a given to understand how they relate to projects just tedious to go through so many pages to understand how screens/schemes differ from each other, if at all. It's very easy to keep creating default copied ones.
Config insights is a gem...many many thanks for the recommendation...but we use Data Center hosted JIRA so can't use it. I could not find a similar hosted app available? Does anyone know one??
@Petru Simion _Simitech Ltd__ Thanks for contributing to Community. When you have a minute, please review our Atlassian Community guidelines for Marketplace vendors and Solution Partners. We would prefer that you identify yourself as associated with the plugin vendor or solution partner before making a recommendation to use such service(s). One way most vendors do this is
for example, by placing the name of your company in your user name in brackets.
We feel this just helps to be much more transparent with end users that might not realize your association with this plugin.
@Andy Heinzer Thank you. Will do.
I assume by the username you mean the Full Name in the Atlassian account.
I did add the company name in brackets but I am experiencing the following problem.
I tried answering recently another question, and I do mention in the answer that the plugin I am making reference to is written by my company. I can see the answer showing after submitting it, however, when I refresh the page, the answer disappears.
How do I request vendor access? It is mentioned in the article that it is advisable but not how do I request it.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events