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

What field in jira is used as the basis for Releases when creating a plan?

New user here.  Created a new plan and brought in one board using Story Points.  THe list of Releases then displays.  Does that list come from the Fix Version field in Jira?


I assumed so but the Scope seems to include Issues without a parent Epic and some of those don't even have a Fix Version value!


1 answer

0 votes
Chiragkumar Rupani
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 28, 2019

Hi Deborah,

Yes, fix versions field of an issue in Jira is used as releases field in Portfolio for Jira.

If your question is why the issues without having fix versions are included in the plan when you have already selected some releases while creating the plan,

then it brings in all the issues from the releases that you have selected while creating the plan and also the issues without any release assigned to it (issues without fixversions).

I hope that helps. Let us know if you have any further query.


Portfolio for Jira Team


We are trying to get visibility into only issues/Epics that do have a Fix/Version. However, since it is including everything in the backlog without a fix/version, it is cluttering up the view in Portfolio. Is there a way to exclude items without a Fix/Version?

(as you can imagine, we have many backlogs documented but not necessarily planning on working on in the near future and want to focus on issues/Epics we have targeted for an upcoming release.)


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events