I’m using JIRA regularly but wonder if there’s a way to track who resolved an issue instead of just the current assignee. Is there a setting to enable resolution tracking?
In my experience, JIRA doesn’t provide a dedicated field that automatically tracks the resolver once the issue is closed. The resolution information is only logged in the issue history, which makes it less accessible if you’re trying to use it in reports or filters. What worked for me was adding a custom field via a workflow transition. I set up an automation rule that captured the current user when the issue was marked as resolved and stored it in a new field. This approach simplifies oversight and makes the resolution tracking process much more transparent.
The challenge of tracking the actual resolver in JIRA has prompted us to explore alternatives over time. In our situation, we addressed it by integrating a plugin that captures resolver details at the moment of resolution without modifying the workflow extensively. This plugin logs the user information directly and makes it usable in reports. Additionally, we experimented with REST API scripts to fetch history data and determine who closed the issues, though that approach required custom scripting. These solutions have added transparency in our tracking process and improved auditability.
In my experience, JIRA’s built-in functionality for logging the resolver isn’t sufficient if detailed tracking is required on a daily basis. I tackled this challenge by incorporating a workflow post-function, which stamps the resolver’s details upon issue resolution, storing this information in a custom field. Although this required some initial configuration work, it has streamlined our reporting process considerably. We can now easily generate queries that filter issues by resolver, providing a clearer audit trail. This method has proven to be both practical and reliable, enhancing overall accountability within our project management system.
hey, try setting up a webhook that alerts you when an issue is resolved. this sends the user info directly. it needs some script tinkering but might work better than custom fields for your needs