All ideas
Sort by:
Trending
Status:
Showing 9041
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
4
VOTE
Manage who receives email requesting document reviewer edit access
Who would benefit? Workspace owners who are currently receiving all requests to edit a document from a reviewer. What impact would it make? The request to edit a document will be reviewed and approved more quickly with less noise to owners that do...
0
Future consideration
13
VOTE
Have the option to enable color-blind friendly mode where ever color is used (e.g roadmaps)
We have the option edit the colors for statuses via the Settings ⚙️ → Account → Statuses and workflows page; however, for users who have color blindness, changing the hue doesn't help much. We're looking to have the option for a texture or pattern...
4
Future consideration
1
VOTE
Note publication and distribution by email on a schedule
What is the challenge? I have a note that contains multiple Aha! views and is presented as a management report on the system to show activity, usage, voting, analytics on customer ideas. In order to view the report (e.g. Senior Managers who do not...
0
Future consideration
1
VOTE
Show embedded views in notes published to portals
What is the challenge? when a Note is defined in the system including Aha! Views this is displayed correctly to users with Aha! named licences (Ideas Advanced) within the application. However if the note is published to a portal, the embedded view...
0
Future consideration
1
VOTE
Publishing Reports on Portal Custom Pages workflow is not intuitive to the user
What is the challenge? As a new user of Aha! and after having read the release notes it is stated that Reports can be published to Ideas Portals. However, the documentation on the Aha! Knowledge Base and application settings are not consistent wit...
0
Future consideration
2
VOTE
Status pills should use the defined color
What is the challenge? Although colors have been defined for a status, the color changes and shows as lighter when in views where the element appears as a pill. What is the impact? Only a cosmetic impact, and doesn't affect other use of Aha! Impac...
2
Future consideration
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
0
Future consideration
11
VOTE
Support parent-child moving across workspaces and Jira projects
In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
4
Likely to implement
13
VOTE
Return unique values against linked epics/features
Using the worksheet at the release level; is it possible to return only "unique" values back against the "linked" epics/features? Example:Release - (linked to Epic 1, 2, 3)Custom Worksheet - Epic Vehicle Brands - Jeep, Dodge Epic 1 -Epic Vehicle B...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved