Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-568

support for build labels within versions

XMLWordPrintable

    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      when working towards a release a number of builds occur. QA needs to be able to tell when something is marked as fixed in version 1.3 whether its actually fixed in the version 1.3 that they are using (e.g. 1.3 build 123 vs. 1.3 build 144) this would be too cumbersome to use in the versions screen.

      a build number has to be tied to a given release since some projects start the build numbers over for each release.

      as for assigning the build number to features, I used to use starteam and it had a cool feature where clicking "resolved" could assign it to the build number of "next", then when the next build number was created/entered, all the existing issues (within that release) with a build number of "next" were assigned to that number.

              Unassigned Unassigned
              d32fc554e6cd Tim Dawson
              Votes:
              172 Vote for this issue
              Watchers:
              91 Start watching this issue

                Created:
                Updated:
                Resolved: