Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-2189

Major / Minor Versions - Sub versions

XMLWordPrintable

    • 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.

      I Searched a bit, and could not find something quite similar.
      This is actually a shared request between Jira / GreenHopper.

      The simplicity of how versions are managed currently is quite good, however ones you couple GreenHopper on top of it, we feel it lacks the ability to organizing versions as a "two level tree"...

      Problem is that a Version to be released may be produced over several planning cycles (Sprints) and as such the current way seems as a slight missfit.

      Weather you wan't to call it a Major/Minor version or something else, I don't know what would make most sense, but if versions was as:

      1.0.0.0

      • Sprint 1 / 1.1.0.0
      • Sprint 2 / 1.2.0.0
      • Sprint 3 / 1.3.0.0

      2.0.0.0

      • Sprint 4 / 2.1.0.0
      • Sprint 5 / 2.2.0.0
      • Sprint 6 / 2.3.0.0

      The sprint items could be used for planning the iterations, while the release notes ect. would be made from the versions.
      So in the above example, Sprint 1 to 3 would lead up to the release of version 1, while sprint 4-6 would lead up to version 2...

      It's a small improvement, but it would make it fit more into places where Release Cycles are not a direct map to planning cycles.

            [JSWSERVER-2189] Major / Minor Versions - Sub versions

            Jens added a comment -

            Hello again.

            Finally got around to upgrade to Jira 4.1 and then GreenHopper 5.0.1 and it works, and Nested Versions does indeed seem to solve what I was talking about, as for Upgrading GreenHopper, I guess it looses backwards compatibility at some point without me taking notice.
            Thats fair enough since I could just upgrade to Jira 4.1 so no biggie (except my limited time )...

            Kind Regards
            Jens Melgaard

            Jens added a comment - Hello again. Finally got around to upgrade to Jira 4.1 and then GreenHopper 5.0.1 and it works, and Nested Versions does indeed seem to solve what I was talking about, as for Upgrading GreenHopper, I guess it looses backwards compatibility at some point without me taking notice. Thats fair enough since I could just upgrade to Jira 4.1 so no biggie (except my limited time )... Kind Regards Jens Melgaard

            Nicholas Muldoon [Atlassian] added a comment -

            Hi Jens,

            Thank you for the clarification. I am closing this issue as nested versions are available within GreenHopper.

            Should you still be experiencing difficulty upgrading GreenHopper please raise a support request.

            Thank you Jens.

            Regards,
            Nicholas Muldoon

            Nicholas Muldoon [Atlassian] added a comment - Hi Jens, Thank you for the clarification. I am closing this issue as nested versions are available within GreenHopper. Should you still be experiencing difficulty upgrading GreenHopper please raise a support request . Thank you Jens. Regards, Nicholas Muldoon

            Jens added a comment -

            @Nicholas Muldoon

            I'm currently looking into Upgrading Jira + GreenHopper, since it seems like i can't get GreenHopper 4.4.1 running on Jira 4.0, also note that this request was based on an ealier version of both products. But I can't quite recall what version.

            But I haven't been able to find that "Nested Version" feature in that install, maybe some settings that has to be in order or something, or maybe it is something that has arrived in some of the latest versions?

            I Expect that when creating release notes for a Version containing Nested Versions, it will compile all issues fixed in all those Nested Versions? (In that case the Release note part is in order i think). A Minor thing is that i prefer to access the release notes through Jira, and i Expect that i then use something in Jira to create them instead of GreenHopper?

            It would be a plus that the Nested Versions was reflected in Jira as well, but not a must I think.

            But all in all ones I'm done upgrading the box that is running Jira, GreenHopper and alot of other stuff ill get back to you with an answer.

            Jens added a comment - @Nicholas Muldoon I'm currently looking into Upgrading Jira + GreenHopper, since it seems like i can't get GreenHopper 4.4.1 running on Jira 4.0, also note that this request was based on an ealier version of both products. But I can't quite recall what version. But I haven't been able to find that "Nested Version" feature in that install, maybe some settings that has to be in order or something, or maybe it is something that has arrived in some of the latest versions? I Expect that when creating release notes for a Version containing Nested Versions, it will compile all issues fixed in all those Nested Versions? (In that case the Release note part is in order i think). A Minor thing is that i prefer to access the release notes through Jira, and i Expect that i then use something in Jira to create them instead of GreenHopper? It would be a plus that the Nested Versions was reflected in Jira as well, but not a must I think. But all in all ones I'm done upgrading the box that is running Jira, GreenHopper and alot of other stuff ill get back to you with an answer.

            Nicholas Muldoon [Atlassian] added a comment -

            Hi Jens,

            Just to clarify, were you raising this to see the GreenHopper nested versions reflected within JIRA?

            As for compiling Release Notes for a release version (from sprints) please see the documentation here.

            Thanks Jens.

            Regards,
            Nicholas Muldoon

            Register now for Atlassian Summit 2010, June 9-11 http://summit.atlassian.com

            Nicholas Muldoon [Atlassian] added a comment - Hi Jens, Just to clarify, were you raising this to see the GreenHopper nested versions reflected within JIRA? As for compiling Release Notes for a release version (from sprints) please see the documentation here . Thanks Jens. Regards, Nicholas Muldoon Register now for Atlassian Summit 2010, June 9-11 http://summit.atlassian.com

            Jens added a comment -

            Added Affected version as the one Im running on, and specified the version under Environment further with what I presume to be build number.

            Jens added a comment - Added Affected version as the one Im running on, and specified the version under Environment further with what I presume to be build number.

              Unassigned Unassigned
              908a536c2a1d Jens
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: