We are working with a client to assess and clean out their JIRA backlog. Given the nature of the huge backlog ~ 500 tickets ranging from 2020 till date .
I wanted to know whether there is functionality of bulk closing the JIRA tickets using CSV file or any other best practices.
Lookign forward to suggestions
Hi @Anshu Mahajan – Amelie from the Appfire team here!
As @Mohamed Benziane mentioned, you could use a global transition in Jira to get it to work!
If you prefer to do it via CSV as you mentioned, you could try out our marketplace app Jira CLI.
With Jira CLI you can get all the issues in a CSV file by running the following command:
--action getIssueList --jql "project = cp AND issuetype = Bug" --file cc.csv --columns "Key"
Once you have the CSV file, you run the below action to move the status of all those ~500 tickets at once.
--action runFromCsv --file cc.csv --common "--action transitionIssue --transition DONE --continue "
Let me know if you have any questions!
Hi,
Yes it is possible. You could also add a global transition in the workflow of each issue type and use it in the bulk edit option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Mohamed Benziane thanks for your reply . Are you able to provide working instructions or link to article that provides steps on adding the GLobal Transitions in the workflow and I can then discuss it with our JIRA developers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here the doc about the workflow
https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.