Hey everyone, I’m having a bit of a debate with my team about how we should handle our JIRA issues. Some of us think we should resolve them, while others say we should close them. I know you can reopen both types, but I’m wondering if there’s any real difference between the two options.
Does anyone have experience with this? What’s the best practice? I’ve noticed that different roles might have different permissions for resolving or closing, especially if there’s a QA team involved.
I’m hoping to find some solid advice or maybe even an official recommendation. That way, I can go back to my team and say, “Look, this is how we should be doing it.” Any thoughts or suggestions would be super helpful!
Thanks in advance for your input!
in our team we resolve issues when dev work’s done, but QA still needs to check. closing is for when everythings 100% finished and approved. it works well cuz QA can easily see whats ready for testing. just make sure everyone agrees on the process or itll get confusing real quick!
From my experience working with various teams, the distinction between ‘Resolve’ and ‘Close’ in JIRA often comes down to your specific workflow and approval process. Generally, ‘Resolve’ is used when the development work is complete but might need final verification. ‘Close’ typically signifies that all work, including any necessary approvals or testing, is fully complete.
In practice, many teams opt for a two-step process: first resolving issues when the work is done, then closing them after a final review or a set period. This approach provides a clear audit trail and allows for any last-minute catch-ups before an issue is considered fully addressed.
Ultimately, the key is consistency. Whatever method you choose, ensure your entire team understands and follows it uniformly. This clarity will streamline your process and improve overall project tracking efficiency.
In my experience, the best approach is to use ‘Resolve’ for most issues.
Resolving an issue indicates that the work is complete from the development side, but it allows for a final review or testing phase. This is particularly useful if you have a QA team or if you want stakeholders to verify the solution before fully closing it.
Closing, on the other hand, should be reserved for when an issue is truly finished and requires no further action. This might be after QA approval or when an issue is deemed no longer relevant.
I’ve found that using ‘Resolve’ as an intermediary step helps catch any last-minute issues before they’re officially closed. It has saved us from reopening numerous tickets that we thought were done.
Ultimately, the choice depends on your team’s workflow, but I’ve seen ‘Resolve’ work well in most scenarios. It provides a clear status without prematurely marking issues as completely done.