How can I export issues in a format that makes it easy to import with changes?

[Austin Mierow]

Problem to Solve:  we are trying to use labels in a more consistent way - but each sprint someone missing a few issues and it requires cleanup. 

Goal: I would like to be able to export all the issues in a sprint in a format that is easy to upload with changes (main use case is deleting one label and adding another)

Where I'm getting Confused; 

What I've tried: the bulk change feature (search and then use the tool) is pretty handy, especially for making 1 change to many issues. We have a couple of changes we need to make for many small batches of issues (add label X to these 3 issues, add label Y to those 10 issues, remove label z from these 3 issues) which becomes tedious when using the bulk edit workflow) 

[Uday Kiran Bhaviri]

Hi I think this can be done using automations. 

You may get an idea by using the below link, you need to change the automation based to your requirement.

https://community.atlassian.com/t5/Jira-Software-questions/Using-Automation-to-delete-a-specific-label/qaq-p/1454447#:~:text=This%20is%20possible%20to%20do,select%20%22Add%2Fremove%20values%22

Hope this will be helpful to you.

[Bill Sheboy]

Hi @Austin Mierow 

What do these labels represent for the different issues?  That is, what problem do they solve?  Knowing this may help the community to offer better suggestions.

Until we know that...

Is the assignment (or removal) of labels predictable based on information in the issue fields?  If so, perhaps an automation rule, triggered on Sprint Started, could perform those updates without the need for manual edits.

Kind regards,
Bill

[Austin Mierow]

Thanks @[deleted] 
I'm trying to categorize the work being done each sprint. I inhereted a Jira system with parameters I need to work around so there are certain settings I can't change. I started trying with Epics and issue types but unfortunately those are linked to other processes. 

The categories I'm trying to parse out are
- Customer Enhancements

- Enhancements for our implementation team 
- Fixes for Support
- Questions for support
- System Maintenance/Tech Debt
- Other


The best way I can figure out to report on these is to make sure each issue has a label and then structure a "count if" spreadsheet that I can export issue data (with those labels)  into

Labels can be many/one so I have to be careful. 

I should Add - @Uday Kiran Bhaviri
But I still will want to audit the entire list at the end of a sprint because my teamates are awesome but they don't always follow process perfectly :-) . . . and neither do I 

[Bill Sheboy]

If the issues and label values need to be manually audited (i.e., cannot be programmatically set / verified) you may want to try this:

• create some saved JQL filters to return the issues of interest
• create a dashboard to show the issues and their labels

At the verification points, the team can use the dashboard to find and then update the issues.