The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Requirements Management - Best Practices
Tim_Kramer
I'm New Here 
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 29, 2020 edited
I have used JIRA many times as a requirements management tool and have always marked the requirements as "Done" once it has been satisfied. Sometimes there are ones that linger around and have not been marked as "Done" so I usually just complete them when grooming through the backlog. I just wanted to get other perspectives out there to see how you are managing requirements and when you mark it as completed. A requirement may have a 1:1 relationship, which is easy, but others will have a 1:n relationship which means that particular requirement would stay open for quite a few Sprints.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian