Restore the remaining estimate when a Requirement is moved from Shipped back to In Development
When a Requirement is shipped the remaining estimate will go to 0, but if that Requirement is re-opened then it will stay 0. Is there a way to restore the remaining estimate when a Requirement is re-opened?
Dale Crane
about 2 years ago
in Features
3
Future consideration
What is the challenge? Using a light color tag makes the white text illegible. What is the impact? One can only assign dark colors to tags. E.g., one cannot create a white tag, a yellow tag, or a very light pastel tag. Describe your idea Allow the...
John Curtis
5 months ago
in Account settings
1
Future consideration
What is the challenge? Currently to-do's are finite meaning we need to raise a pile of them and they do not show dependencies What is the impact? Long dislocated to-do list Describe your idea Allow for to-do nesting and dependencies
Guest
5 months ago
in Notes
0
Future consideration
It should be possible to import releases on a product line level. Any level of workspace hierarchy which supports the creation of any records should also support the bulk import of these records via csv.
Guest
almost 3 years ago
in Releases
0
Future consideration
Allow users to add comments on published presentations
Actually, logged users can add comments on presentations inside Aha! but it may be interesting to allow non-Aha! users to comment a published presentation (public URL, restricted by password or not). Visually, it may be simply a Comments icon over...
Guest
almost 9 years ago
in Presentations
2
Future consideration
Better interactive tools for Presentations and Webpages
The current Presentation and Webpage solutions have very limited interactive capabilities for external users. This limits the value we provide, as the 'self service' features are limited mainly to read-only actions and not true interactivity. As a...
David Barber
about 1 year ago
in Presentations
0
Future consideration
Aha! Scorecard on Release apply to Master Features and Features
Title. Allow an "Aha! Score" which is applied at the "release" level to allow apply and synchronize to the "linked" Master Features / Features for Product Workspaces.
Guest
over 3 years ago
in Releases
2
Future consideration
Support timestamps on status change dates in the API
I would like to have timestamps supported in the API for any user action oriented dates (like create dates, updated dates, etc.). Currently the timestamp is not included for the status_changed_on field. I'd like for timestamps to be supported for ...
Erin Ward
over 1 year ago
in API
0
Future consideration
Support linking the Aha! URL field to the Azure DevOps Hyperlink field
Goal: We want to see in DevOps which Item it syncs with in Aha! Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single ...