I’m trying to figure out if there’s a way to track who an issue was assigned to when its status changed in JIRA Cloud. Our team’s workflow involves lots of back-and-forth between devs and QA. We often reassign issues multiple times during this process.
Here’s what typically happens:
A dev finishes work and assigns it to QA for testing
QA finds a problem and sends it back to the original dev
The original dev might then pass it to another dev to fix
We want to know who the issue was assigned to at each status change, not just the final assignee. Is there a JQL query that can give us this info? It would be super helpful for tracking our workflow and improving our process.
Has anyone figured out how to do this in JIRA Cloud? Any tips or workarounds would be appreciated!
hey there, i’ve had similar probz. jira cloud doesnt support historical assignee tracking natively in jql. you might set up a custom field to record assignees on status change, either manually or via automation. not perfect, but worth a try. cheers
I’ve grappled with this issue in my organization too. While JIRA Cloud doesn’t offer built-in historical assignee tracking via JQL, we found a workaround that’s been quite effective. We implemented a custom field called ‘Previous Assignee’ and set up an automation rule to update it whenever the assignee changes. This way, we can track the last assignee for each status change.
To make it work, we created a transition screen that forces users to select the new status and update the assignee simultaneously. It’s not perfect and requires some user training, but it’s given us valuable insights into our workflow patterns. You might also consider using the JIRA API to pull this data if you’re comfortable with some light scripting. It’s a bit technical, but it can provide more comprehensive historical data if that’s what you need.
Unfortunately, JIRA Cloud doesn’t provide native functionality to track historical assignees via JQL. However, there are some alternative approaches you could consider. One option is to utilize a custom field to log assignee changes, potentially automating this process. Another method involves leveraging JIRA’s automation rules to capture and store assignee information when status changes occur. For a more comprehensive solution, you might explore third-party add-ons that specialize in advanced reporting and analytics for JIRA. These can often provide deeper insights into historical data, including assignee tracking. While not ideal, these workarounds can help you gain the visibility you’re seeking into your team’s workflow patterns and assignee history.