We can't pay for a feature already available in the previous project.  

We can't accept a cancellation of a feature.

Best,

I believe it was "resolved" as a duplicate of JSWCLOUD-17260 " Release option in Next-Gen projects".

The Swanly spam comment was just spam.

Agreed, completely unacceptable "Resolution" to this issue.

We enabled full support for release functionality in Next-Gen projects in app Swanly release timeline for Jira Cloud.
You can create release for Next-Gen project, access Releases screen and assign versions to Next-Gen issues. just like in classic projects.

There is much more features available in the app eg. Visualisation of releases on Timeline, Adding custom stages to releases, cross-project releases…
(I'm the product owner of the app)

https://marketplace.atlassian.com/apps/1219470/swanly-release-timeline-for-jira

Esse recurso é mt importante para o release. Pfv incluam logo q possível.

Indeed a must to have feature

BTW where is the voting link I couldn't find any? 

Definitely need this!  Seems like it's already being worked on..??  Checkout the sidebar of this screenshot, pulled from the Next Gen Roadmap.

This is super important!  otherwise next gen is really nice

Please, don't spam. Use the voting link instead of typing '+1'

+1

This eeems entirely obvious. Also, the next-gen release calendar hasn't been updated since last Fall. Any update from Jira?

+1

+1

+1 

I need this

+1

Must deploy...

+1 

Need this feature urgently to manage our software projects on Next Gen. Our Tasks, Stories & Bugs Lists are getting larger and larger by day, already very difficult to manage.

+1

+1

another feature we are missing , seems like we are not in next gen but somewhere in 1950 when options were limited to nearly none and people were happy to have few.

@Jira we are in 2019 the time of AI, Machine learning, Wakeup plz

Thanks!

It's on the website as a feature......

+1, silly to have removed it without telling anyone.. bad form

+1

+1

+1

+1000

+1 only point which holds us back from migrating.

+1

+1

+1

100% needed.  No way we'll upgrade until this functionality is incorporated.

Essential for us.

+ 1

Yes, Releases are needed before using next-gen.

Yes Please !!!

Very essential for us.

For Beginners it is very difficult to follow older infromations about jira, when you remove some functionality like versions.

I believe this request was originally created based on our requirement - at first I thought I missed something but glad to see there are others that also see this as a major missing feature. We are stuck using classic when the new features such as roadmaps are available on next-gen.

Agreed, I'd really like to use Roadmap, but I gotta have release/versions so Next Gen is no use to me.

this is very important feature for managing any software! now the problem, i think learning the classical version is a waste of time, and using next-gen is waste of time and money !! 

This is a show-stopper for us migrating to next-gen projects. It is useless without release feature.

Since we already have the ability to connect Jira to bitbucket, one kinda expects to have the ability to have some connection between merges to a designated release branch (indicating releases in Bitbucket) and releases/versions in JIRA. 

roadmap without release like:  a boat with lot of treasures on it, has no haven to land.

I really liked the classic versions/releases and hope that will find its way to the next-gen boards soon.

In the meantime I use labels for versioning my issues and can filter on these labels to check what has been changed since last version.

I second this - 

Currently trying to decide if i use a classic board without a roadmap, or a next-gen board without versions/releases