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
            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?
            Hide
            eduardo1786380273 Eduardo Sponda added a comment -

            Managing project which involves microservices or APIs is hard with Jira. I was trying to figure out how to manage component versions and I could find workarounds only. Now with this ticked is clear to me that it's impossible to do it without a workaround.

            Show
            eduardo1786380273 Eduardo Sponda added a comment - Managing project which involves microservices or APIs is hard with Jira. I was trying to figure out how to manage component versions and I could find workarounds only. Now with this ticked is clear to me that it's impossible to do it without a workaround.
            Hide
            ben.arundel Ben Arundel added a comment -

            A project has many elements like services, databases, web-front ends etc, all can have different versions, there is currently no way to manage this within Jira without separating out into projects which is cumbersome at best. Versions for components is now an essential requirement.

            Show
            ben.arundel Ben Arundel added a comment - A project has many elements like services, databases, web-front ends etc, all can have different versions, there is currently no way to manage this within Jira without separating out into projects which is cumbersome at best. Versions for components is now an essential requirement.
            Hide
            sremiszewski Stan Remiszewski added a comment -

            I am a newbie to JIRA. My approach is the assign EPICS to define the subcomponents/modules of the project and use versioning on EPICS to assign the modules to a release. Tasks to be complete (i.e. module features) are then created within EPICS and subtasks can be created within the tasks. In the Backlog view EPICS and tasks are assigned to levels and easily filtered. In report view EPICS are captured and estimates are visible by EPIC, Version and individual, assigned to and individual tasks. I do not see the immediate value in components. Considering they are like projects with the benefit of actually being projects JIRA doesn't do much with them that adds value for the complication of another layer. BUT... I am willing to learn...

            Show
            sremiszewski Stan Remiszewski added a comment - I am a newbie to JIRA. My approach is the assign EPICS to define the subcomponents/modules of the project and use versioning on EPICS to assign the modules to a release. Tasks to be complete (i.e. module features) are then created within EPICS and subtasks can be created within the tasks. In the Backlog view EPICS and tasks are assigned to levels and easily filtered. In report view EPICS are captured and estimates are visible by EPIC, Version and individual, assigned to and individual tasks. I do not see the immediate value in components. Considering they are like projects with the benefit of actually being projects JIRA doesn't do much with them that adds value for the complication of another layer. BUT... I am willing to learn...
            Hide
            schrepfler1 Srđan Šrepfler added a comment -

            What I do is apply a convention, I prefix the version with the component name and then I use the capability where I can assign multiple versions to a ticket.

            Show
            schrepfler1 Srđan Šrepfler added a comment - What I do is apply a convention, I prefix the version with the component name and then I use the capability where I can assign multiple versions to a ticket.

              People

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

                Dates

                • Created:
                  Updated: