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

As Product Owner I want to assign Epics (with all its stories) to a Version

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 4
    • 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.

      Currently it is not possible to assign whole Epics to a version.
      It is possible to add all Stories of an Epic to a version using d&d, but we still do not see Epics in a Version...

      Because we usually release Features (Epics) and not individual Stories in a Version (production release) it is hard for us to track which features are in a version.

          Form Name

            [JSWSERVER-9009] As Product Owner I want to assign Epics (with all its stories) to a Version

            this would be very useful especially in very complex programs not o go too deep to find the versions.

            Herve VAUTIER added a comment - this would be very useful especially in very complex programs not o go too deep to find the versions.

            I would also like to request this feature get prioritized please and thank you!

            Nadim Jamal added a comment - I would also like to request this feature get prioritized please and thank you!

            +1

            Julian Bauer added a comment - +1

            Up voted!!

            Miguel Silva added a comment - Up voted!!

            Come on!!!!!! 

            Enrique Weber added a comment - Come on!!!!!! 

            Hi Tom. 

            I apologise for assuming you were with Atlassian, perhaps I was being hopeful that anyone from them is actually reading this stuff.. clearly not! Thank you for your time and suggestions, I hope they are helpful to some people; they seem like a pretty good work-around. 

             

            Ben

             

            Ben Findlay added a comment - Hi Tom.  I apologise for assuming you were with Atlassian, perhaps I was being hopeful that anyone from them is actually reading this stuff.. clearly not! Thank you for your time and suggestions, I hope they are helpful to some people; they seem like a pretty good work-around.    Ben  

            tmecbox55 added a comment -

            Hey Ben...I am not with Atlassian...I'm a user just like you .      I am not a developer and found the Jira automation very easy to use....it is not scripting to point and click menu drive functionality to build rules.  Takes just 5 or 10 minutes to do.  If you know who your project administrator is, they most likely can do this if they have some technical knowledge.  

            Regards and hope this helps you,

            Tom 

            tmecbox55 added a comment - Hey Ben...I am not with Atlassian...I'm a user just like you .      I am not a developer and found the Jira automation very easy to use....it is not scripting to point and click menu drive functionality to build rules.  Takes just 5 or 10 minutes to do.  If you know who your project administrator is, they most likely can do this if they have some technical knowledge.   Regards and hope this helps you, Tom 

            In other words it can't be done, but if you the availability of a Jira scripting expert, they can work round the system if they have enough knowledge, experience and access right. 

            It's a shame that your software is so hard to use that it requires scripting to do things which seem obvious. 

            Ben Findlay added a comment - In other words it can't be done, but if you the availability of a Jira scripting expert, they can work round the system if they have enough knowledge, experience and access right.  It's a shame that your software is so hard to use that it requires scripting to do things which seem obvious. 

            tmecbox55 added a comment -

            Hi....I believe this can now be done using the Jira Automation functionality now part of the platform.     You'll need to have administrative priv. to the project, and should be able to create a Jira Automation rule that is scheduled to run periodically or on create of an epic, to copy the fix/version field of the epic to all underlying stories.   

            One approach would be to schedule a rule to run periodically looking for Epics that have the Fix/Version field populated. Add a branch then for Stories or other issues in the epic, and edit the underlying stories to copy the fix/version field to them from the epic. 

            I've been using the Automation functionality now for about a year and it provides a great deal of functionality to automate repetitive tasks, enable consistency in our use of standards, and notification of exceptions or other conditions in a given backlog and make adjustments.   

            tmecbox55 added a comment - Hi....I believe this can now be done using the Jira Automation functionality now part of the platform.     You'll need to have administrative priv. to the project, and should be able to create a Jira Automation rule that is scheduled to run periodically or on create of an epic, to copy the fix/version field of the epic to all underlying stories.    One approach would be to schedule a rule to run periodically looking for Epics that have the Fix/Version field populated. Add a branch then for Stories or other issues in the epic, and edit the underlying stories to copy the fix/version field to them from the epic.  I've been using the Automation functionality now for about a year and it provides a great deal of functionality to automate repetitive tasks, enable consistency in our use of standards, and notification of exceptions or other conditions in a given backlog and make adjustments.   

            It is quite evident that Atlassian are not interesting in making quality software or supporting or caring for their customers. The quality of their software has been actively dropping for years, and they simply milk this poor product for all it is worth. This suggestion has been up for 10 years, it would be easy to implement, but nothing has changed in Jira for a very long time now. It is not really fit for purpose and there are lots of good alternatives around. I strongly suggest Hansoft as a much better tool which does all of this and more.

            Ben Findlay added a comment - It is quite evident that Atlassian are not interesting in making quality software or supporting or caring for their customers. The quality of their software has been actively dropping for years, and they simply milk this poor product for all it is worth. This suggestion has been up for 10 years, it would be easy to implement, but nothing has changed in Jira for a very long time now. It is not really fit for purpose and there are lots of good alternatives around. I strongly suggest Hansoft as a much better tool which does all of this and more.

              Unassigned Unassigned
              0a68dd5f2cbc Janos B.
              Votes:
              199 Vote for this issue
              Watchers:
              125 Start watching this issue

                Created:
                Updated: