All ideas
Sort by:
Trending
Status:
Showing 8935
4
VOTE
When creating a new Ideas record, you cannot add new Tags values like you can in the same field on the edit screen
When working with Ideas directly in Aha! (not via the Ideas portal) there is a discrepancy with how the Tags field works. On the Create ideas form, the Tags field does not allow you to add new values (see attached Create Idea Tags field no results...
2
Future consideration
4
VOTE
Provide a warning explaining consequences when changing the workflow used in a workspace
When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...
1
Will not implement
13
VOTE
Prioritize search results with exact matches
Using a real example: We have a single idea in our system with the word "Tagging" in its title. Entering the word "Tagging" into the search bar results in a large array of results where the partial match "tag" features somewhere in the item (e.g. ...
0
Future consideration
1
VOTE
Don't Allow Jira Integration to Fail Based on One Field
What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...
0
Future consideration
9
VOTE
Ability to adjust report element hierarchy
In pivot and/or list reports, I often have the original report correct but then need to adjust what is the master record and/or how the elements are related. I also have had this issue with custom roadmaps. Right now, I have to take snapshots of t...
0
Future consideration
28
VOTE
More visualization options for strategy diagram
The circular diagrams in the strategy section(Vision & Diagram) do not visualize well on today's browsers and monitors. Text is too small, data overflows. A more simple Left to right hierarchy would be more understandable, sharable and viewable.
9
Future consideration
4
VOTE
Maintain cycle time data when team workflow is changed
Currently if I select a new workflow for my team and map my statuses to new statuses, I lose all past cycle time data because cycle time only focuses on the current workflow being used. Instead, I would like to see historical data that coincides w...
0
Future consideration
18
VOTE
When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.
The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
5
Future consideration
2
VOTE
Display named range value on Overview tab "Initial estimate" field
Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Currently, the "Initial estimate" field includes the resulting time-based estimate, but not the range I've selec...
0
Future consideration
2
VOTE
Embed notes in record description (same appearance as whiteboards)
Who would benefit? Product teams build up documentation relevant to specific epics and features. You can currently add this document to the Research tab or add it as a link in a record description, but this does not give a user a preview of what t...
0
Future consideration