Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Atlassian Update – 31 December 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are not currently any plans to implement this suggestion.

      This request is in a simlar position to JRA-846: We absolutely understand many the logic behind many of the requests for versioned components, but we strongly believe that our focus should be on making JIRA simpler and easier to use. Simply put, versions for components is likely to add complexity on a conceptual level, at a technical level (more bugs and slower performance) and will lead to a more confusing UI.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Original request description:

      I am a JIRA Administrator responsible for configuring it for complex development environment. Just like the entire project, the components also have their version number. Many times we have projects made up of multiple smaller applications, DLLs or modules. Each component in JIRA should have a list of versions just like the project. That way will be able to release and schedule versions of components.

        Attachments

          Issue Links

            Activity

            Hide
            carl.blanchard Carl Blanchard added a comment -

            I couldn't agree more, the screen shots I attached to this issue demonstrates that versions could be easily added to the UI
            Components and Versions are a fundamental concept in software, so why don't they just build a system which caters for both. Easy and Complex and let the users decide if they require a easy or hard to use UI...

            Gee's Atlassian you could even do a bit of A - B testing to actually see what the users use...

            Show
            carl.blanchard Carl Blanchard added a comment - I couldn't agree more, the screen shots I attached to this issue demonstrates that versions could be easily added to the UI Components and Versions are a fundamental concept in software, so why don't they just build a system which caters for both. Easy and Complex and let the users decide if they require a easy or hard to use UI... Gee's Atlassian you could even do a bit of A - B testing to actually see what the users use...
            Hide
            philip.hadley141896281 Phil Hadley added a comment - - edited

            Our project is a mobile app, which consists of 5 components, and I plan to model ALL FIVE as JIRA Components. To handle the lack of versioning support for JIRA Components, I plan to simply increment the project version any time any of the components are versioned. We will document the mapping of component versions to Project versions outside of JIRA.

            For example,

            • Project A version 1.0
              • Component X version 1.0
              • Component Y version 1.0
              • Component Z version 1.0
            • Project A version 1.1
              • Component X version 1.0
              • Component Y version 1.0
              • Component Z version 1.1
            Show
            philip.hadley141896281 Phil Hadley added a comment - - edited Our project is a mobile app, which consists of 5 components, and I plan to model ALL FIVE as JIRA Components. To handle the lack of versioning support for JIRA Components, I plan to simply increment the project version any time any of the components are versioned. We will document the mapping of component versions to Project versions outside of JIRA. For example, Project A version 1.0 Component X version 1.0 Component Y version 1.0 Component Z version 1.0 Project A version 1.1 Component X version 1.0 Component Y version 1.0 Component Z version 1.1
            Hide
            tamsin1 Tamsin Slinn added a comment -

            Personally, I create versions in JIRA which include the component name. So for example I would have versions in the list such as utils-1.2, server-1.0 etc
            Outside of JIRA, e.g. tagging and releasing, I just use the number. It works for us.

            Show
            tamsin1 Tamsin Slinn added a comment - Personally, I create versions in JIRA which include the component name. So for example I would have versions in the list such as utils-1.2, server-1.0 etc Outside of JIRA, e.g. tagging and releasing, I just use the number. It works for us.
            Hide
            florian.rubin986649047 Florian Rubin added a comment - - edited

            My company creates software which rely a lot on modules, pluging, components, and we are really annoyed by this lack of functionality at this point :/
            I start to think that Jira is maybe not accomplished enough to manage the hole development and bug tracking of a company.

            PS: Making a software easier to use don't mean less functionality.

            Show
            florian.rubin986649047 Florian Rubin added a comment - - edited My company creates software which rely a lot on modules, pluging, components, and we are really annoyed by this lack of functionality at this point :/ I start to think that Jira is maybe not accomplished enough to manage the hole development and bug tracking of a company. PS: Making a software easier to use don't mean less functionality.
            Hide
            northam.tim264259252 Tim Northam added a comment -

            Hi,
            I think versioning at a component level would be a good idea. Currently it is not possible to use a JQL to determine the last release via a subset of the application. What happens when you have separate code bases individually deployable and you want to quickly and easily identify the latest release? Is the only way to use separate projects even though some tickets relate to both code bases-common features between the phone and tablet code bases.
            What is the best way to use JIRA with micro services infrastructure?

            Show
            northam.tim264259252 Tim Northam added a comment - Hi, I think versioning at a component level would be a good idea. Currently it is not possible to use a JQL to determine the last release via a subset of the application. What happens when you have separate code bases individually deployable and you want to quickly and easily identify the latest release? Is the only way to use separate projects even though some tickets relate to both code bases-common features between the phone and tablet code bases. What is the best way to use JIRA with micro services infrastructure?

              People

              • Assignee:
                Unassigned
                Reporter:
                jason nethercott Jason Nethercott
              • Votes:
                608 Vote for this issue
                Watchers:
                342 Start watching this issue

                Dates

                • Created:
                  Updated: