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; } } }

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

Deborah Fein

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!

Comments

Chiragkumar Rupani

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.

Regards,

Portfolio for Jira Team

LG_bpk5ox

Hello,

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.)

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

advanced-roadmaps

fix-version