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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.