The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Retroactively adding data to historical Jira issues (labelling etc)

Anett Hunt
June 20, 2024

Hello!

I was wondering if it is possible in Jira to enhance the data modelling of historical ticket or project data. Specifically, if this can be achieved through the existing Labels feature or by creating new data fields, and whether this can in any way be applied retroactively to historical data.

For instance, I believe you can filter through tickets using keywords and automations to potentially label tickets (or bulk updating). Are there any other possibilities to quickly scan through approx. 10k tickets?

EDIT: Does anyone know of any apps or integrations for Jira that could do the job?

Thank you!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

3 votes
Ste Wright
Community Champion
June 20, 2024

Hi @Anett Hunt 

You've mentioned two native features:

  • Automation - to find the issues, and add context (like labels)
  • Bulk Updating - from the search menu

But there's also CSV Import - you could export a list of the issue keys, modify the data in CSV, then re-import it in. See more on this help page, specifically this section:

Updating existing issues

To update existing issues, your CSV file needs to contain a column that maps to Issue Key. If an issue exists for a given key, it will be updated.

---

There are Apps also, check out options such as...

Ste

TAGS
AUG Leaders

Atlassian Community Events