count of status/issuetype usage? project activity?

[Bryan Collick]

I'd like to clean up a JIRA instance and would like to

• list all issuetypes and status by usage
• list all projects by activity in a given time period

I'm hoping this would give me insight into inactive projects, issuetypes and statuses that have been added over time and could be removed.

How would you do this? I don't think I can do this using JQL so I was thinking of seeing if JIRA support in chartio might easily allow me to get this information

[Niclas Sandstroem · Accepted solution]

I would not contemplate of cleaning out some things depending on how old it is. For example issuetype is something I would keep to eternity despite mistakes. I would then make sure it's not used for new projects.

I would definitely use JQL to view on activity of projects. JQL that comes to mind is for example:

created < startOfYear("-1") and created != startOfYear("-1")

I would then move these projects into hiatus by stripping permission etc to avoid JIRA to have to check towards them on searches. Of course after checking if they are not needed for anything.

If its a big instance and more then I could bother to write in JQL manually I would utilise the REST API.

[Bryan Collick]

Hi Niclas!

You're right; instead of "cleaning out" or "removing," things I should have used the verb "deprecate" instead. I don't intend to delete anything; my aim is to do a proper administrator's job by archiving unused projects and defining a preferred list of issuetypes and statuses that project administrators should use when working in their projects. 

Your JQL would definitely show me which projects are active, but it would not show me any projects that have not been active in that time period. These projects would be at the top of the list of what I'm looking for so that I can strip permissions, etc, as you've noted. 

I'm not familiar with using the REST API directly, but I believe that is what Chartio or Tableau or other BI visualization tools utilize in their reporting. What query would you use when using the API? I'm hopeful you might know table names as I'm not super familiar with JIRA's db schema.

[Niclas Sandstroem]

If your not familiar with programming maybe that is not the best to approach REST API.

Some other ideas has bounced on this site:
https://answers.atlassian.com/questions/239867

https://answers.atlassian.com/questions/129235

https://answers.atlassian.com/questions/297430

https://answers.atlassian.com/questions/19136839

https://answers.atlassian.com/questions/134760

My JQL was just an example you should be able to review projects not being use by looking at when a issue in it was last updated for example. How big of a instance is it?

[Bryan Collick]

Not being familiar with programming and not being familiar with using the REST API are two different things. 

Thanks for the links; I think they give me a good sense of what's available via querying the database directly. 

[Niclas Sandstroem]

Good luck and yeah I agree but that said I would most likely go by SQL/JQL myself but all depends how big of mass I was trying to handle. 

Then I would consider also trying https://marketplace.atlassian.com/plugins/net.seibertmedia.jira.plugins.project-archiver/server/pricing depending on how much work/time/cost I was facing