Hey everyone,
I’m a bit confused about the difference between resolving and closing issues in JIRA. Our team is having a debate about which one to use, and I’m trying to figure out the best practice.
As far as I know, you can reopen both resolved and closed issues. But I’m wondering if there are any practical differences between the two options, apart from the permissions required to perform each action.
Does anyone have experience with this? What’s the standard approach in your team? I’d really appreciate some insights to help settle our debate and establish a consistent workflow.
Thanks in advance for your help!
In my experience, the key difference lies in the workflow stages. Resolving an issue indicates the task is complete from the assignee’s perspective, but it may still require review or testing. Closing, however, signifies the issue has been fully addressed and verified.
Our team uses a two-step process: developers resolve issues upon completion, then our QA team closes them after verification. This approach ensures quality control and provides a clear audit trail.
One practical advantage of resolving first is that it allows for easier tracking of issues that might need reopening if problems are discovered during final checks. It also helps in generating more accurate metrics for team performance and project progress.
Ultimately, the choice between resolving and closing depends on your team’s specific workflow and quality assurance needs.
i’ve used JIRA in a couple projects and here’s my take:
resolving is like saying ‘i think its done but someone should check’. closing means ‘its definitely done, no more work needed’.
we usually resolve when dev finishes, then QA tests and closes if all good. keeps things organized and makes sure nothings missed.
I’ve been using JIRA for several years now, and I can share some insights from my experience. The main difference lies in the workflow and finality of the action.
Resolving an issue typically means the work has been completed, but it’s awaiting verification. It’s like saying, ‘I believe this is done, but let’s double-check.’ This allows for a review process before final closure.
Closing an issue, on the other hand, is more definitive. It signifies that the issue has been fully addressed, verified, and no further action is needed. In my team, we use ‘Resolve’ when the developer completes the task, then our QA team verifies it before changing the status to ‘Closed.’
This approach has worked well for us, providing a clear distinction between completion and verification stages. It also helps in tracking issues that might need reopening if problems are found during final checks.