-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
11
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem Definition
At the moment, the schedule and reports pages only display open tickets (open in the Portfolio-sense, that is decoupled from the actual JIRA issues status). This is due to the fact that the schedule was designed to show future data and requires the items to be displayed to have a calculated start and end date as well as assigned teams, releases, sprints, etc.
However, having an option to show completed issues / historic data in the schedule and reports page would add a lot of value. This would require storing the last calculated values (including start and end dates) on the issue before closing it in Portfolio. It might also require additional filter capabilities b/c including all past issues, the timeline could get significantly longer and more difficult to read.
Suggested Solution
Add an option to show completed issues/historic data in Schedule and reports.
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
JPOSERVER-1226 Filter "Open and completed" issues is not honored in some views
-
- Closed
-
-
- Gathering Interest
- links to
[JSWSERVER-25134] Allow to show completed issues in schedule and reports pages
Any update about resolution?
We current have the same problem: Closed issues show up in Roadmap but not in Program...
Come on guys, it can't be hard to show all the completed issue across projects? We use Portfolios multi-project release feature and it's weird that it's not possible to see all the done issues easily for a release.
We are not developing software but we do use (and love) Portfolio to visualize the work within our team.
Having a toggle to show also completed work would eliminate the need for reporting to management.
It would be huge benefit: we would save time AND we would be able to show management a nice continuity from our completed work into our upcoming work. Win-win!
Looking forward to it! It shouldn't be too hard to pull off...
Dave White
added a comment - The function of depicting everything, included completed issues, on the Portfolio timeline is important for reporting purposes and should be a function of Jira Portfolio. The fact that it isn't is actually astonishing.
Dave White
added a comment - The function of depicting everything, included completed issues, on the Portfolio timeline is important for reporting purposes and should be a function of Jira Portfolio. The fact that it isn't is actually astonishing. Any news about it?
More teams in our org are starting to use Jira and following roadmap in a consistent way is really crucial for us (from up to down) then this bug is getting really on the way.
We use Target Start & End date fields to visually provide roadmap commitments for our initiatives; on the target schedule view it would be great to visually tell a story on committed dates (target start/end) and the actual scheduled start/end dates and compare how teams are performing. Currently with the completed work filtered, the scheduled start is always calculated to the latest start for an issue and the history behind the actual work is lost visually on the plan.
For leadership teams it's very important to see this on the plan - todays view almost makes it seem like work has just started even though there could be months of work already completed.
Commenting to add an additional request. Upon introducing Portfolio for Jira to leadership - they were enamored by the great features. However, they would also like to view previously completed sprints to tell the entire story of agile transformation from the portfolio perspective. We would love to see this feature introduced to foster tool adoption as we scale.
Portfolio is a reasonable tool for reporting project progress to management, and reduces the need to waste time preparing reports offline. It is a common need to include recently completed work in such a report, and including completed epics / stories would fulfil this need.
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