Proper JIRA Program Tracking

[Samuel Levine]

There is a company that has been using JIRA for a long period, but as of recently there has been numerous tickets that were created in the past (hundreds if not thousands) that are not relevant to any program that we are currently working on or plan to be working on in the future.  As I look at these tickets I notice that some are tied to existing programs (JIRA tickets), but I was wondering if there is a way to remove these unused JIRA tickets and close them and clear them out?

The company is also working to try and use tempo as a time tracker, but they are not clear under the providing forecast hours within Tempo, does anyone have an examples that tempo can be used to plan properly?

[Tom Lister]

Hi @Samuel Levine

for your first question on removing issues, your standard options are:

from a filter list of affected issues, bulk process the results to achieve one of

- make the Close transition

- actually delete the issues

- move to an “archived” project