All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5862
1
VOTE
Calculate work done from best estimate
What is the challenge? A release’s capacity can pull from the best estimate of its features. However, in order for the release show work done when a feature is completed, the feature must have had a detailed estimate or had actual effort logged. Y...
0
Future consideration
1
VOTE
"Hide from Shared Views" Button for Now, Next, Later Roadmap
What is the challenge? The only way to hide an epic from a now, next, later roadmap is to wholly filter it from the report. We convey different info to different stakeholders/teams in the org and, for example, will often hide certain epics from sa...
0
Future consideration
1
VOTE
Daisy-chain steps in a framework
What is the challenge? Steps, by their nature are conducted in sequence or parallel with interconnecting inputs, outputs, processes and loops. Representing these structurally with process sequencing would be awesome. What is the impact? Improved c...
0
Future consideration
1
VOTE
Custom fields for framework steps
What is the challenge? Ability to capture structured data of our choosing on steps. For example, frameworks represent parts of or a whole system. Systems have inputs and outputs. It would be great to be able to capture inputs and outputs for a ste...
0
Future consideration
4
VOTE
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.
0
Future consideration
4
VOTE
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...
0
Future consideration
32
VOTE
Have workflow status change dates refelect the most recent date a status was set
The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...
6
Future consideration
5
VOTE
Support large volumes of repos in GitHub integration
My company has been migrating from GHE to GitHub.com, and the default repo permission is set to "internal". This is causing individual users to have access to over 15k repos. In Aha, this large number of repos is preventing users from being able t...
0
Future consideration
4
VOTE
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.
0
Future consideration
20
VOTE
Make workflow status description visible for everyone
The configuration of work flow statuses is a great tool to customize your view in aha. Unfortunately the Status descriptions are only visible in the configuration mode (which is only available for a specific typ of user). This leads to confusion f...
4
Future consideration