Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to create version in Jira properly?

Tags:

tfs

jira

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.

like image 296
vikasde Avatar asked Feb 11 '10 17:02

vikasde


People also ask

How do I manage versions in Jira?

On the Releases or Versions screen, find the version you want to edit. Select the actions menu ( ) > Edit. Edit the version's name, start and release date, and description. Click the Save button to save your changes.

How do I add a fixed version to Jira?

To create new Jira fix versions inside Easy Agile Roadmap's, select the 'Add version' button. Versions can be dragged and dropped on different dates on the roadmap; this will automatically update the fix version's start and end date in Jira.

Does Jira do version control?

Implementing Jira + version control means less jumping in and out of different interfaces, which can impact development productivity. P4DTG works with your own Jira server or with Atlassian's Jira Cloud.

What is the difference between release and version in Jira?

Releases represent points in time for your project. They can be used to schedule how features are rolled out to your customers, or as a way to organize work that has been completed for the project. In Jira Software, each release is called a version.


2 Answers

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.

like image 142
Vladimir Alexiev Avatar answered Oct 27 '22 00:10

Vladimir Alexiev


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.

like image 29
Hugo Palma Avatar answered Oct 27 '22 00:10

Hugo Palma