I’m trying to understand the best practices for handling issues in JIRA. Our team is split on whether to resolve or close issues when we’re done with them. I know you can reopen both resolved and closed issues, but I’m wondering if there’s a practical difference between the two options.
Does anyone have experience with this? What’s the recommended approach? I’ve heard that different permissions might be needed for resolving vs closing, especially if there’s a QA team involved. But are there any other factors we should consider?
I’d really appreciate some guidance on this. It would be great to have a clear reason to choose one method over the other, so we can all get on the same page. Thanks in advance for your help!
Having worked with JIRA for several years across different teams, I can share some insights. The main difference lies in the workflow and finality. Resolving an issue typically means the work is done but awaiting verification. It’s like saying, “I think this is fixed, but let’s double-check.” Closing, on the other hand, is more definitive - it’s the final step that says, “This issue is completely done and verified.”
In my experience, the best practice is to use a workflow where issues are resolved first, then moved to a ‘Ready for QA’ or similar status, and only closed after passing QA. This gives clear visibility into what’s ready for testing and what’s fully completed.
Regarding permissions, you’re right that they can differ. In some setups I’ve seen, developers can resolve issues, but only QA or project managers can close them. This adds an extra layer of quality control.
Ultimately, the choice depends on your team’s process. If you have a dedicated QA phase, the resolve-then-close approach works well. If not, you might just use ‘Close’ when work is complete. The key is consistency across the team.
From my experience in project management, the distinction between resolving and closing issues in JIRA is crucial for maintaining a clear workflow. Resolving an issue indicates that the assigned task has been completed, but it’s still open for review or testing. Closing, however, signifies that the issue has been fully addressed, verified, and requires no further action. In practice, we’ve found it beneficial to use a two-step process: first resolving issues when the work is done, then closing them after a final check or QA approval. This approach allows for a quality control stage and helps catch any overlooked problems before finalizing the issue. Regarding permissions, it’s common to restrict closing rights to team leads or QA personnel, ensuring an extra layer of oversight. Ultimately, the choice between resolving and closing should align with your team’s specific workflow and quality assurance needs.
in my experience, resolving means the work’s done but needs checking. closing is final - issue’s completely done. our team uses resolve first, then QA checks, then close. it keeps things clear n organized. but yeah, permissions can be different for each. just pick what works for ur team and stick to it