Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

Possible to have 2 Release fields in Roadmap?

Is there a way to add a second Release (Version) field to the roadmap?


For example, the Release field in the Roadmap maps to the "Fix Version" field in the Jira issues view. 

In the Jiras issue view, I have also enabled the "Target Version" field. Is there a way to add it to the Roadmap? Checking the Ad Custom field section in the roadmap, I can't make out if any of the listed items maps to Target Version field.

Essentially, it doesn't need to be Target Version field in specific, I'd just like to get any second Release/Version field to the roadmap that maps to a field in the Issues view

1 answer

1 accepted

0 votes
Answer accepted
Curt Holley Community Leader Feb 14, 2022

Hi @Anna Poppe 

I presume your "target version" field is a custom field that you (or someone) has created? 
If that field is a free format field, then it would be deemed an unsupported custom field for an Advanced roadmap plan.

Although we can now edit the Description field, free format fields cannot be added into a plan to be selected in the fields section and used to filter on.

That said, I understand that it might be difficult to have such a field be anything but free format.

Just making assumptions, please correct me if I've headed down a wrong path.

Hi @Curt Holley

In this case, the target version field refers to the same releases set up within the project as the fix version field - so I guess it's not a free format field?


Essentially, I'll create filters that show both the Fix and Target Versions (=Releases) of certain Epics. This part is the simple part.

I just like to use the Roadmap to create tickets, update release versions, sprints or dates etc - so if I could have two fields that use the releases of the project that would make updating these easier, as I spend a lot of time time in the Roadmap :D

Curt Holley Community Leader Feb 14, 2022

OK, sounds like a "version picker" field. Which is not a supported field for AR. See:
Enable custom fields used in Advanced Roadmaps in Jira | Jira Software Cloud | Atlassian Support



Thanks for your help tho, much appreciated @Curt Holley !

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events