I’m using standard JIRA, but it only records assignees and reporters, not resolvers. Is there an option to enable tracking of the user who closed an issue?
While JIRA does not track the user who resolves an issue by default, I have found that this functionality can be achieved through workflow customization. In my experience, adding a custom field or a post-function that captures the user who transitions the ticket into a resolved state is a reliable approach. This solution not only records the resolver but also allows for greater flexibility in reporting. It might take some additional setup, but it has significantly improved our ability to audit issue transitions over time.
I encountered a similar challenge in our setup where the details of who closed the issue were essential for our post-incident audits. Instead of just modifying transition screens with custom fields, we integrated a targeted API call triggered on issue resolution that recorded the actor into an external database. This solution required additional scripting, but it provided us with a clear audit trail and helped in maintaining accountability. It also seamlessly integrated with our logging system, giving us the flexibility to analyze resolution data along with other operational metrics.
hey there, i run a simlar workaround by hooking a custom event to log th closer. it’s not a builtin feature, but a quick post func script did the trick. hope this helps!
The challenge of tracking who actually resolved an issue can be addressed by taking advantage of automation within JIRA. In our case, we implemented a script listener that detects transitions into a resolved state and stamps the issue with the actor’s details, essentially creating a custom field that logs this information. This approach, while not native to JIRA, provides a clear audit trail. It requires some initial setup and testing to ensure consistency, but it has proven beneficial in maintaining an accurate record of issue resolutions over time.
Over the years I have experimented with several approaches to solve this issue without relying on native tracking. In my case, leveraging Jira Cloud’s built-in automation has proven very effective. I created an automation rule that triggers on issue resolution, which then automatically updates a custom field with the identity of the resolver. This method is less intrusive than custom scripting and maintains compatibility with future Jira upgrades. The setup also simplifies the audit process once it’s in place, providing clear insights into team performance over time.