Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
Ian Cooper
over 2 years ago
in Account settings
1
Future consideration
What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest
about 4 years ago
in Features
4
Future consideration
Ability to Pull Estimates onto the Prioritization Report
Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...
Guest
about 1 year ago
in Features
2
Already exists
Add delivery risk check for missing initial estimate
We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.
Jeff Tucker
about 1 year ago
in Capacity planning
0
Future consideration
Add Parking Lot Releases and Features to Feature Roadmap and Release Gantt
Who would benefit? What impact would it make? I want to track upstream (pre dev) work in product and UX's lane to track true status end to end for our work. How should it work? When going into the features roadmap view I am trying to see my parkin...
Karla Johnson
about 1 year ago
in Releases
0
Future consideration
A way to track your progress with meeting deadlines and how many times they are moved. This could be integrated with capacity planning, but per user. I would like to see my personal capacity across all features and To Dos and keep track of it. Thi...
Guest
over 9 years ago
in Features
1
Unlikely to implement
Support milestones in the release retrospective report
The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.
Jeff Tucker
about 1 year ago
in Reports
0
Future consideration
Send report notification ONLY if there is data in the report
If a report returns no data then the notification shouldn't be sent via email. It should only send the notification if there is at least one row of data.
Steven Schafer
over 1 year ago
in Reports
0
Future consideration
As a manager of business analysts I want to see the definition "burn down" of a given feature, epic, or initiative over time. For example, how much of a given epic or initiative is being defined vs. ready for development vs. ready for release etc....
Guest
over 5 years ago
in Reports
0
Future consideration
Need to roll up product initiatives to outside portfolio initiatives
Our Aha hierarchy is built out where are portfolios are fairly separate but still will have some dependent work. It would help us track those dependencies a lot clearer to have the rollup allow product initiatives to roll up to portfolio initiativ...
Wen-Wen Lin
over 5 years ago
in Strategy
1
Future consideration