Bulk change tickets to prior assignee

[Amine Errazi]

It was common practice for us to have a Testing status on the board where the ticket is reassigned to the person testing, then that same person transitions the tickets to Done.

So now,  we have a large number of tickets left with the assignee being the tester vs the dev that worked it.

I am looking to bulk edit the issues affected to the dev/engineer that was working on them.

Assumptions:

Ticket(Issue) is transitioned to In Progress by the assignee

The branch is created by the assignee. Commit is performed by the assignee

[Daina Tupule eazyBI]

You can create a report in eazyBI to see who moved issues to a specific status.

Please use a dimension Transition Author on Rows to see a user who did a status change in the issue. Measure Transitions to issues count on Columns will give you issues moved by a user. Add Transition Status or Transition dimension to Pages and select either status or a particular status change you would like to use to identify the developer.

Then you can use the option drill through issues to see specific issues. You can open them in the Jira issue navigator and apply bulk changes to those issues. 

Please note you can open only up to 100 issues at a time with this approach. Add some additional dimensions, like, status, project, time, etc. to pages to limit issues per user.

Please check this report in our demo account for some more ideas.

Daina / support@eazybi.com

[Amine Errazi]

Thank you Diana!!

[Bill Sheboy]

HI @Amine Errazi 

To provide some context for the community to offer suggestions/ideas:

• What problem are you trying to solve by assigning the issues back to another person?
• What would you do with that information if you had in now?

As you have described the use case, you could solve this by:

1. manually asking the team to re-assign issues before moving them to done,
2. adding custom fields to capture the names of the people in development and testing roles (from the issue transitions), and add Automation for Jira rules to capture the values and to assign/re-assign as needed after the transition to "done".

Best regards,
Bill

[Amine Errazi]

Thanks @Bill Sheboy for the reply.

The problem: Not able to know which dev worked on a ticket since the assignee was changed to the tester.

--> Why? I need to know points completed per dev for tickets with a certain label 

----> Why? I need to quantify how much R&D each dev worked on (R&D tax credit initiative)

Back to the problem, I want to clarify that I am looking to retro-adjust old tickets, not necessarily what to do moving forward.

Doing it manually will be overkill, unfortunately.

I am currently using eazyBI to run a script that in theory can identify who transitioned the old ticket to in progress, and make the assumption that it's the same person that worked on the ticket.

Any other creative suggestion is welcome :)

[Trudy Claspill]

Jumping in rather than starting a separate response thread.

If you are able to get a report of the issues the includes the name of the person to whom you want to re-assign the issues, then one way you could execute a bulk change would be to

1. organize the list by the person to whom you want to reassign the tickets

2. In Jira, execute a search for the issues that would be assigned to one of those people

3. Use the Bulk Change feature to change the Assignee on those issues.

4. Repeat steps 2 and 3 for each person to whom you want to re-assign tickets.

[Bill Sheboy]

Thanks for clarifying, @Amine Errazi  

I'm not eazyBI savvy, so I am unable to offer ideas with that approach.  You may want to add a tag with eazyBI to this question to see if that gets more community members looking at this.