I would like to be able to set the starting iteration number
I have had a couple times where it would be nice to be able to set the "first" iteration number. One, where I was setting up a team that had been doing iterations for two years, and I wanted an easy way to make project look like what they were used to. Another was when we needed to set up a second project within the same company-- basically forking the development. We needed separate tracker projects and priorities, but it would be nice to keep the numbering in sync. I know the trick of "back-dating" a story (and have done that twice), but just having a number would be easier.
6
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?Interesting idea, it currently isn't in the road map of new features for Tracker, but if enough people like this idea we can consider it.
-
Inappropriate?I like this idea. Also, if you are starting a new product release it would be nice to start from 1 instead of 265!
-
Inappropriate?i like the idea too! we started using Tracker after using other solutions and so Iteration #1 doesn't make sense for the first iter we're doing in Tracker.
-
Inappropriate?Agreed, we are starting to use Pivotal with Sprint 16. Would love it to say Sprint 16 as that is what we are communicating to the client
-
Inappropriate?You could backdate dummy stories with import to fake this. But what a pain.
Loading Profile...





