Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

Can you change the Release field that Portfolio looks at?

Justin Bunde
Justin Bunde Mar 30, 2020

Currently the Release field in Portfolio looks at the "Fix Version" in the actual JIRA tickets.  Can you change this to look at a different field or a custom field?  We are starting to use Program Increments and would like to create a custom field moving forward.

Answer
Watch
Like Roi Fine likes this
431 views

1 answer

0 votes
Roi Fine
Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 30, 2020

Hi Justin,

I'm sorry but you can't map fix version to a custom field. I'm curious to learn why you prefer a custom field over the fix version field.

Cheers,

Roi

View More Comments
Justin Bunde
Justin Bunde Mar 31, 2020

We currently use the "Fix Version" field to in our task/bug tickets to identify which software build the fix was built into.  So essentially it is used as a historical tracker field after the task/bug is completed.  The Release field in Portfolio is/should be used to determine which release you are planning to submit the fix into.  In our case we are using Program Increments to plan our future releases.  If we could map to a custom field, we would use a new field in the task tickets called Program Increment that would map directly back to Portfolio.  This would then be our planning field and Fix Version would be our historical reference.

Like
Roi Fine
Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 31, 2020

Interesting stuff, thank you. I'm still not sure why you would need two fields and not one. Is it for the sake of program increments reporting? 

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events