How do I enable "Fix version" and "Affects version" for Bug issues?

[Matt Pennock]

Hi All,

I would like a drop down to associate a bug with affected software version(s) when the bug issue is created, and another drop down to associate a bug issue with the version where it is fixed when the bug issue is completed. I believe these features are normally called "Fix version" and "Affects version".

I have enabled the Releases feature for my project, have have multiple releases. I can add the "Fix version" field to issues (bug/story/task) but there is no way for me to add "Affects version".

How do I enable an "Affects version" feature?

Is it possible to create my own issue fields that auto-populate with versions from my project?

Thank you,

Matt

EDIT:

An example of searching for "affects version":

It seems this feature is available for "Data Centers and Servers" (https://confluence.atlassian.com/adminjiraserver/issue-fields-and-statuses-938847116.html). Are "affects versions" not available for cloud?

[Mikael Sandberg · Accepted solution]

Hi @Matt Pennock,

Welcome to Atlassian Community!

Team managed projects does not have the option to add Affected version and have it linked to Releases. This can only be achieved if you are using a company managed project. 

[Bill Sheboy]

Hi @Matt Pennock -- Welcome to the Atlassian Community!

Adding to what Mikael notes: here is the suggestion to add Affects Version for team-managed projects.  You may vote for/watch it to see progress.
https://jira.atlassian.com/browse/JSWCLOUD-18747

Kind regards,
Bill

[Matt Pennock]

Thank you Mikael and Bill! I'll talk to my admin about setting up a company manage project in the meantime.

[Daniel Schealler]

Hey guys,

Is there a way to convert a team managed project to a company managed project?

We're on Jira Cloud and I have Affects version available in one older project, but can't add it to a newer project. Trying to get the new one to follow the pattern of the old one and it's full of bugs and issues already and I don't want to restart from scratch if I can avoid it.

[Daniel Schealler]

Aaah, okay, scratch that. Just checked out the ticket above and I see that 'team-managed' is just the latest Atlassian-speak for next-gen projects.

Bugger. Can't make it work, but may be able to make it work in the future. Frustrating but it is what it is.

[Gerard Cattin]

The field was marked as Hide in the core list so first I had to make it visible then things worked.

[Gerard Cattin]

Rodney, Using that Default Field Configuration on a Software company-managed project I don't see that field (Cloud premium):

[Rodney Nissen - ReleaseTEAM]

Just tested it on a default "Bug Tracking" Project on Jira Cloud.  Affects version is available for cloud too.  You might need to set up the field to be available for your project.  Go to Project Settings -> Field, and make sure Affects Version is listed on the list.

Next step would be to check the screens.  Be sure the field is included on the screens that would show for bugs.

Then confirm the field is listed.

[Daniel Schealler]

Hey Rodney,

Just to add a little context: I can add Affects Versions using screenshots like yours when I look at older projects - what Atlassian is currently referring to as 'company-managed' projects.

But on 'team-managed' projects (formerly next-gen) we can't do that yet.

Just adding this as clarification for anyone else stumbling on this that may be confused.

I have an older project where the project settings looks exactly like your screenshot above. But it's old.

The new project that was added recently-ish, that I'm trying to get to conform to the way my old project used to work, instead has a settings page that looks like this: