XMLWordPrintable

    Details

    • Feedback Policy:
      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 An updated workflow for server feature suggestions.
    • Current Status:
      Hide
      Atlassian Update – 20 December 2017

      Hi all,

      Thank you for all your votes and comments on this suggestion. We realise it took us long to update the status of this suggestion - thank you for your patience.

      We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to invest in allowing versions of components in Jira.

      While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level.

      Also there are commercial third party apps available, that provide the requested functionality:

      Since investing in versions of components in the Jira Server is not aligned with our strategy and roadmap, we will be closing this issue.

      Meanwhile, we've decided to prioritise other top voted suggestions for the near future:

      • Improved Rich Text Editor
      • Reduction of challenges related to Mail Server 
      • Handling Jira email chattiness
      • Allowing users to edit shared filters and dashboards

      I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our approach to highly voted Server suggestions here.

      Please don't hesitate to contact me if you have any questions.

      Regards,
      Gosia Kowalska
      Senior Product Manager, Jira Server

      Show
      Atlassian Update – 20 December 2017 Hi all, Thank you for all your votes and comments on this suggestion. We realise it took us long to update the status of this suggestion - thank you for your patience. We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to invest in allowing versions of components in Jira. While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level. Also there are commercial third party apps available, that provide the requested functionality: S ubcomponent and component version Configuration managment Toolkit . Since investing in versions of components in the Jira Server is not aligned with our strategy and roadmap, we will be closing this issue. Meanwhile, we've decided to prioritise other top voted suggestions for the near future: Improved Rich Text Editor Reduction of challenges related to Mail Server  Handling Jira email chattiness Allowing users to edit shared filters and dashboards I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our  approach to highly voted Server suggestions here . Please don't hesitate to contact me if you have any questions. Regards, Gosia Kowalska Senior Product Manager, Jira Server

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      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

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: