We have a custom workflow where the issues to to a status "Ready for Release" when the team has completed its job. One or several sprints later, these issues might then get released in production, and the status is set to "Closed".
The problem that I now have is that story points are only counted when the issue is set to "Closed", which from a team perspective might be the wrong sprint. Is there a way to define other statuses as "story point worthy"?
A sprint has a very simple boolean flag of whether something is "done" or "not done". There's no grey area, an item is one or the other.
Your suggestion that "closed might be the wrong sprint" implies your process is not matching what Scrum does - the whole point of the sprint is that all items should be started at the beginning of the sprint and done by the end of it, not carried over
Jira's boards work off the last column to work out that done flag. So yes, to consider another status as "done", map that status into the last column alongside "closed"
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.