New features for next-gen projects in Jira Software Cloud: Releases and Versions

[Anton Pogodin]

Hey guys, where is the Affected Version field? :(((

[Nazar]

Not bad)

[İsrafil Dilmeç]

Finally. An important feature that will make life easier.
Thank you.

[Oriol]

Excellent news!

[Indrek Petti]

Could we get also filtering and visual representation of assigned fix versions on the board and on the backlog? 

[John Ly]

Hey Team, one big feature we use a lot from the old gen version is 'Version reports' any update on when this will be released?

[Mathieu Ghennassia]

Issues related to a released version should be hidden in the backlog and in the board as well. Is there something in the settings that I am missing?

Can we disable the auto hide rule after ~15 days?

[Jonathan Muir]

The doc says that there should be a Version filter on the Backlog and Board once the Releases feature has been activated and a version or 2 created.   But the filter remains missing?  

Quote from https://confluence.atlassian.com/jirasoftwarecloud/releases-and-versions-980451731.html

Filter issues by versions

On the board or backlog, select the Versions filter to show issues from specific versions and hide the rest.

[Gonchik Tsymzhitov]

So nice features!

[Jo Pinto]

Yes! Really needed this.

[whammy]

Hi Everyone,

Thanks for the feedback so far! We're planning on bringing the following features to next-gen versions and releases:

• Board clearing
• Filtering by version (initially backlog but looking at board)
• Bulk assigning issues to versions via the backlog.

We are looking at introducing other features also, so please keep the feedback coming!

Cheers,

Gareth

[RaeRo]

Can the same release be used across multiple next-gen projects?

[Greg McElroy]

Is there a plan to add an affects version field? We find this field extremely useful in our classic projects, especially for bug tracking. 

[Tyler]

Finally!  I used this feature extensively in another JIRA version and have greatly missed it in this version.  

[Tuan Tang]

Hello  Member Support nearby 

The project ready need   a teamwork

Thank You For Support 

[Jim Nordal]

Yeah

[crypton1]

Great! Especially if below is add its a very nice feature:

• Board clearing
• Filtering by version (initially backlog but looking at board)
• Bulk assigning issues to versions via the backlog.

[Ronan Quillevere]

Any idea when the reports associated to Versions will be available in NG ? 

[David Wuth]

AffectsVersion is a critical part of releases/versions for us, in terms of tracking bugs. We cannot move to NG projects without that field in addition to FixVersion.

[Oriol]

That's really good, it could be also very useful to have custom fields in the release like "Release incident" or  "Release notes".  Also it could be great to make the pre-defined release notes field open to changes.

[Nathan Neufeldt]

I made the mistake of creating an NG project without realizing it didn't have the 'Affects Version' field. This has made tracking issues a pain as we have several developers and QA working on different branches and determining which branch introduced the bug when merging an upstream version becomes time consuming. Thank goodness we haven't released our project to our customers yet as this would be a nightmare to track and update them.

Please add the 'Affects Version' field as soon as possible.

[Krzysztof Kozlowski]

The Next-gen projects are still missing "Affects versions" field which make them unusable in real product-related projects. It's the basic field when working with bugs affecting different releases. When can we expect adding it?

[manasak]

Hello, When is the estimated date to access these new features! We very much would like these!

[Tal Levi]

Is there a releases and Bitbucket integration? It would be great if every issue that's related to a commit that was committed to master/production would be tagged with a release version automatically. Would be much more efficient, and very helpful especially with continuous deployment.

[Tommy Tate]

We use JIRA cloud with 90% of our projects as JIRA “classic”. Release coordination is done using fix version for client (iOS / Android) and a diff fix version for API releases (daily).

migrating to next gen won’t be possible until fix versions work across classic and next gen projects. Seems like a fundamental requirement for migration, given that it is unrealistic to migrate the 90% of projects over to next-gen in one go.

Will you be supporting cross project (classic <> next-gen) release and fixVersions?