-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
8.20.0
-
8.2
-
1
-
Severity 3 - Minor
-
Issue Summary
When a user configures a new Portfolio plan or edit an existing plan, they will be given an option to select specific version that they want to include in the plan. At the version selection plan, Portfolio displays the following message:
Select the releases you want to track in your plan. Only the issues of selected releases will be included in the plan.
However, in the next step, Portfolio will include issues without any version as well as issues with the selected version.
Environment
- Jira Portfolio 3.11.0
Steps to Reproduce
- Create a new version in a project and ensure that no issues have new version as Fix Version.
- Create a new plan.
- Use the project which the new version belongs to as the plan source.
- Select the newly created version.
Expected Results
Portfolio only displays issues with the selected version in its fix version field.
Actual Results
Portfolio will include both the issues with the selected version in its Fix Version field and also any issues without any Fix Version value.
Workaround
Create a filter that only includes issues with a specific version and use it as the issue source.
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24945] Portfolio includes issues outside of the selected version
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center