Backlog is a great tool for issue management, no doubt about it! I'm a happy user.
But now that we have released version 1.0 of our product we are getting more into release and quality management processes also.
We have an OTAP environment and want, as an example, keep track what issues are where in the pipeline to know at any given point which issues to test before moving to production. Which issues need be tested? Which ones are moved to pro-productions etc. etc.
Is there any best practice guidelines anyone can give on how to do this with Backlog? For example: since the status range (open, in progress, Resolved, Closed can not be extended, I can not use that to keep track and make a difference wether it's resolved in test environment, but still has to undergo Quality checks in pre-production stage.
Anyway, I was hoping someone has figured out a good best practice how to incorporate release management into Backlog.
Thanks and keep up the good work!
Please sign in to leave a comment.