nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Affects Version/s built-in field non-editable

Emily Howell

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

Accepted answers

Nic Brough -Adaptavist-

Have you added any versions to the project yet?

All comments

Nic Brough -Adaptavist-

Have you added any versions to the project yet?

Emily Howell

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

Nic Brough -Adaptavist-

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

Emily Howell

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?

Richard Cross

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration