Loading Profile...
Deployed release marking should be easier.
We do acceptance on stories, but that's different from deployment, and there's no easy way currently to do both, other than adding labels to the dozens of stories in an iteration which is quite tedious. I'd like to be able to add / edit the sequence of story states to contain a "deployed" after "accepted". I could understand that not everyone would want this, but I do. The other way to do this could be to have the current releases be named milestones, which is what it effectively is, and add a separate designation of releases that you can drag and drop finished stories into.
I’m frustrated
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Our development process is different from our deployment process too. Essentially, we use 'accepted' to indicate a story is now in the master build.
But deployment is a multi-stage process for us. (We have distinct staging, production, and benchmarking environments) It would really save us a lot of time if we could add a way to indicate the deployment state of a story.
