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

+1

Up voted!!

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

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. 

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.

Currently I need to search stories under those Epics I want to assign to a version, and do bulk update.
It will be good if we have option in Epic to assign all linked stories to the same version of Epic. 

• It must be an option, leave PO to decide, in case there are stories in the same Epic may be delivered in different versions.

Super Important! Please add 

Essential

Yes, essential

Yes Please

+1 it will be helpful.

Also interrested.

yes please

Much interested

+1

+1 this would be a huge help in planning

Also interested

Very interested as well.

Still very interested in this ability. Adding epics to versions help create organization for what efforts were included in a version - rather than a line item list (which is helpful, but can be an eyesore on large projects).

The ability to add Epics to Versions is absolutely vital, and really critical to add. Without it, it's impossible to neatly schedule a project. Without the ability, Versions and Epics get confused, overlap, and are virtually duplicates of each other, with very little value add.

Would be very useful since adding every story related to an Epic would only add those and not stories that are created in the future. Assigning a epic to a version would also enable a inherent due date from the version down to the epic.

Would be very useful for us too

Hi In our App Agile Tools & Filters we've implemented some features that will help you on your use case:

• Version labels on Epic Panel list for Epics which are directly assigned to a version 
• Visibility of Epics directly assigned to a version without any stories - once you select a version,  Stories assigned to this version will be shown. But you won't be able to drag them to empty Epics which are assigned to the same version. Once you select "Include Epics for selected option" you'll se those epics and you'll be able to do proper planning. That is useful if you've got a lot of epics and versions. 

Have a look at the screen

This would make Jira a lot easier so please implement this.

I too want this.

I too want this. I know others at my company want this. Release planning at the Epic level makes more sense than trying to show a gantt chart of the progress of 900 stories. Your competitor Rally does this already. 

Would be great to have the backlog view display a more meaningful hierarchy, with Versions<<>>Epics<<>>Stories.

Not sure how big a challenge this is, but we're just breaking the pre-established metaphor here when we get to the Version panel of the backlog.

We need to slice big chunks of scope.

These chunks need to be tied to versions.

We can't just "ballpark" the actual scope implemented for an epic by browsing its 900 closed tickets.

Really surprised this hasn't been upvoted more. Basically the bigger the project..the more likely team(s) are to benefit from version planning using epics.

If i want to see or plan what's in a version I can see 10 epics - making it clear what's in there rather than a 100 stories... 

Our app Exocet for Jira can offer you a handy way to implement this in Jira. As Atlassian hasn't yet made this available in their core product, it can be a solution for those of you who need this feature. If you need help on your implementation journey, feel free to reach our support.

This would be a useful feature please implement

We would also appreciate the feature

I'm not sure if this applies to Jira Cloud or not, but +1

Can this please be implemented soon.

This would be very much appreciated as it support the overall consistent set up of a Release structure.

This feature would make the UI consistent and speed up assignment.

+1

+1

+1

This would be amazing. 

We are looking to connect epics with versions as in allows tractability of requirements into development plan and in epics for regulatory compliance

Indeed I'm trying to organize the many epics that have ben have created... some of which are simply not scheduled to get done in the upcoming release. would be very helpful to assign epics to the a specific version via drag and drop

+1

+1

Yes, please.

Badly needed for product development in my company. 

Reason is, the product manager looks at epic level, this is where the product planning takes place. Stories are for teams, they are of too low granularity to do major releases planning.

Also, ability to easily assign epics to versions + the requested feature to aggregate stories' time estimates within an epic would give us a really good tool for long-term capacity planning. 

+1

+1