Managing two versions for Version picker fields


Is that possible to have two versions dictionaries within the same project?

What I need is to have default field Affects Version/s to use the Version Dict1 and some other field, lets say Committed Version to operate the Version Dict2, dicts should be managed by admin only.

The field should look pretty the same, but different dictionaries should be carried.

I've tried the Label type of new field (doesn't match the expectations, dictionary is modified by anyone on the flight) and Multi-select searcher (is pretty good, but I want to unify the UI for both)


Thanks in advance, any suggestion is appreciated.

1 answer

0 votes

No.  The whole point of the version fields is that they draw their values from the same list.

But you could simply add a standard select list to the issues with a totally different list.  It won't be versions, but it'll do the job.

Hi, Nic.

Thanks for your advice.

Unfortunately, standard select list does not match my needs here - as I need sometimes to select 2-4 or even 5 versions for the field, whereas the select list allows to choose only two, even though there are sub-versions of each field.



Pavel Bussel

Ok, so use a multi-select list.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

245 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you