Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bulk change of Epic Link in Next-Gen Project



it seems to me the bulk change does not work pretty well while having classic and next-gen projects at the same time.

In my Next-Gen project, I want to make some bulk changes to several Stories and add them to existing Epics in the same project. As shown in the screen, the Epics are only listed via "unlabelled-[KEY]" instead of using the Epic name. I assume, the selectbox here only refers to the old field name of the classic projects?


BTW: The reason I want to add several Stories to an Epic via bulk change is, because I can not find any other way in the Backlog than adding each and every single Story to the Epic. Ctrl + Click for multiple selection does not help since there is no menu nor context-menu to perform some actions on the selection.
EDIT: I just found the menu in the Backlog for this activity which is the (...) menu on a single issue. This does not work in many cases probably and just happen to work the first time after a page refresh (F5).



1 answer

0 votes

Hi Lars,

It looks like you're running into an existing bug, which can be found here:
Please be sure to watch it, so that you are notified when this is fixed in a future release.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events