Filter with report column of user who changed the status

[Dave Bair]

I am looking for some help on a Jira query / filter.   We are about to do a significant cleaning of the backlog and I am trying to create a report that shows all the tickets we rejected.   That part is easy, what I am stuck on is how to get the "rejected by" person in the report.

Filter JQL that is returning the right list of tickets

project = FORM AND status changed TO Rejected after 2024-11-05

Now I want a column in the report to tell me who Rejected that ticket.

[Petru Simion _Simitech Ltd__ · Accepted solution]

You can use CIFJ - Issue History For Jira

https://marketplace.atlassian.com/apps/1235591/cifj-issue-history-dashboard?

hosting=cloud&tab=overview

The app is recently released by our company.

You can search and filter issue history using the field Updated By.

Once you obtained your desired result you can either use the list of issues or export to CSV.

[Dave Bair]

Thank you for the insight, and the tool.  We have installed it in our app on a trial basis and I am getting good results.   

I am having a bit of a hard time getting the filters to work just right though.

I can get the ones in Rejected that had a change in the last week - that is perfect!

However, when I add the criteria to only report when a status changed, I am getting no results.  Can you help me understand what I am doing wrong?

[Petru Simion _Simitech Ltd__]

Hi @Dave Bair 

I am looking into it. Will do a few tests and let you know.

Glad you like the rest of the functionality.

Regards, 

Petru

[Petru Simion _Simitech Ltd__]

Hi @Dave Bair 

I tested and the search works correctly. Please see attached img.

1. What I see is that you were able to add multiple statuses with label Rejected in your search field.  That shouold not be possible, as Jira does not allow adding multiple statuses with the same label. The Status drop down field allows multiple values, but once you added a value you can not add it again. When you click the drop down, you will see all statuses that have not yet been added to the field. At the beginning, when you have no values selected, you see all the statuses ordered alphabetically. Do you see more than one value for Rejected? If you do try clearing your cash and try again. 
2. If you want to search for the user that moved an issue into status Rejected, then all you need to search for is the value Rejected in the field Value To. If you select also the Rejected value in the Status field, you are searching for a field for which the status was changed to Rejected that is still in the Rejected status. Which can give you less records. Not sure about your use case but an issue can be moved into Rejected status and later moved into another status. You might want to filter for: Field Updated - Status and Updated to - Rejected.

The tool works like this.

You need to select a Project. Otherwise the search result can be unpredictably large.

If you just select the Project and hit Search, history for all issues in that project will get displayed in the table below.

If you select any values for the other fields, the result will be filtered to only match values accordingly.

If you populate more fields, the result of the search is an AND. 

For example: Field Updated = Status and Value To = Rejected will return all issues where the field that was updated is the Status and the value that the user updated the status to is Rejected. 

Hope this helps.

What I am interested in is how those multiple values of Rejected could be added to the Status field. Please test again after clearing your cache and let me know.

Thanks.

Regards, 

Petru

[Dave Bair]

I also thought the multiple copies of Rejected in the Status search selector was odd.   I am seeing multiple versions of all the statuses I use in my project.  I am *guessing* this is because we are a large enterprise and different projects use different statuses, so the tool somehow views each of those iterations as a unique value.

I was thinking I could attempt to find the "right version" of Rejected in the list (try them one by one), although that assumes they are sorted alphabetically and by id so they present in the same order each time.

[Dave Bair]

I was able to isolate the correct version of Rejected (third of five) and got the long list of results again with a single entry in that box.

However, when I add the Status in the Field Updated and Rejected in the Value To, then I get no results.

Per your earlier comment, yes I am specifically looking for tickets that were

• In the FORM project
• Changed in the last week
• Are currently in the Rejected Status
• Were Rejected in this last week

And I am trying to report basic ticket information, and specifically WHO Rejected the ticket.

[Petru Simion _Simitech Ltd__]

Just do a first search for Project FORM and Field Updated = Status. Do you have any results?If yes, do you see any value "Rejected" in the column Updated To?

About the fact that you have multiple statuses with the same name it looks weird.

Statuses are global. They are used across projects.

As an admin:

Go to [your_company_name]/secure/admin/ViewStatuses.jspa

You can see that you can not add a second status with the same name.

If you go to this page, how many Rejected statuses do you see?

[Petru Simion _Simitech Ltd__]

Hi @Dave Bair 

The reason you are seing multiple roles with the same name is because they come probably from Team Managed Projects. We are going to implement a change in the app to deal with this. Will keep you updated.

[Petru Simion _Simitech Ltd__]

Hi @Dave Bair 

The Status filter field was changed to a simple text.

You can now add manually the value of the Status name you intend to filter.

Thanks for rising up this issue

[Trudy Claspill]

Hello @Dave Bair 

Welcome to the Atlassian community.

That will not be possible if you have only the native Jira JQL functionality available. Native JQL and results display is very limited in what it can filter against and display related to issue history.

There are at least a couple of alternatives you could consider:

1. Look for a third party app that would help you get the data you want.

2. Develop a custom extraction using the Jira REST API

If this is something that you think will be an ongoing need and you don't want to use a third party app, you could set up a custom field and an Automation Rule (or add to the workflow) to set the custom field to the user executing the Reject transition.

[Yuliia_Borivets__SaaSJet_]

Hi @Dave Bair 

I think the method with custom field + automation might work for you.

If you are open to using apps, you can check out Issue History for Jira developed by my team. It provides a separate column and filter for "Updated by" person.

Here, I have a similar post: How many Jira issues were rejected after testing?