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
4,331,501
Community Members
 
Community Events
169
Community Groups

Affects Version/s built-in field non-editable

I have not changed any properties of the Affects and Fixed Version/s built-in fields, however, when I try to edit them (either at Issue creation or during Issue update) these fields are pre-populated with "None" and are not editable. Has anyone experienced this before or can tell me if I need to set something somewhere?

Many thanks in advance, Emily Howell

2 answers

1 accepted

0 votes
Answer accepted

Have you added any versions to the project yet?

No - I did wonder this as there is the select list renderer option, however, I cannot see where you would add versions?

Go to the project summary and look for "maintain versions" - you need to add one or more versions to get them on the list!

Is this functionality only used when in connection to Stash, or some other source code control tool, i.e. it pulls the version from there?

I have now found where I can add versions from the Project Summary page. Thank you Nic for prompting me on where to find this.

I have now found where I can add versions from the Project Summary page. Thank you Nic for prompting me on where to find this.

Thanks a lot for helping me out as well.

Aside from the accepted answer, "Affected Version/s" and/or "Fixed Version/s" need to be present in the relevant Screen to be editable. 

It's a bit confusing because if either field happens to have a value, both with be displayed in the issue view.

To further confuse things, when either field is not editable by a Project Admin (or lower) a JIRA System Administrator looking at the same issue will be able to edit the field.

Suggest an answer

Log in or Sign up to answer