How do you version in JIRA when your versions are like 4.8.{TFSBuild}.{TeamCity.Build}? Do I simply create a 4.8 Version in Jira? However what would I set the release date to? The problem is that our versions are dynamically and created based on the build# from tfs and the Team City build#. What is now the best way for me to create versions in Jira? Only the Major.Minor is hardcoded for now and for every few bug fixes we upload the release to the live server.
+2
A:
I would suggest to name the upcoming version that doesn't have a fixed name yet something like "Next release".
When you actually do release that version then you can change the version name in Jira to reflect the correct name.
Hugo Palma
2010-02-12 16:05:54
I'm fighting the same problem as vikasde, and I think this approach is best. Something like 4.8-dev until you release something to your customers. You could use a custom field to track the specific development build if you need to.
quip
2010-03-02 20:37:32
+1
A:
Jira versions are primarily a planning tool (especially if you use Greenhopper aka Agile, where you can have a version hierarchy). So that's different from a build. It may take a thousand builds to achieve the functionality planned for a "FixFor" version.
On the other hand, "Affects" versions are used to track in which build a particular bug was found. So it'll pay to rename the "current version" (when you mark it as Released) to the actual build, as Hugo suggests. And cleanup/close/move any outstanding issues at the same time.
Vladimir Alexiev
2010-03-03 14:14:35