Application
Sort by:
Trending
Status:
Showing 7554
63
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
12
Future consideration
1
VOTE
Using filters dynamically based on logged on user attributes (in reports)
What is the challenge? A user may belong to an organisation that has particular attributes assigned using custom fields. It would be useful if filters on reports (thing a portal) could be preset based on these attributes What is the impact? When u...
0
Future consideration
2
VOTE
Shade an entire row or column in a table on a whiteboard
What is the challenge? Shaded columns and rows help the user visible see what is a header versus what are cells/data. Currently you can shade table rows/columns in the text editor, but you cannot do so in Whiteboards. What is the impact? You have ...
0
Future consideration
2
VOTE
Standardize the formatting of AI-generated release notes
What is the challenge? When we generate release notes, we rarely get the beautiful results showcased in the Aha! blog post: What is the impact? The formatting is inconsistent. This causes me to have to go back and manually edit/update each release...
1
Likely to implement
2
VOTE
Enhance approval API to allow approval group to be set
What is the challenge? Managing approvals across many features efficiently What is the impact? Without using approval groups we would need to update all feature's approvers each time someone joins or leaves an approving team Describe your idea I w...
0
Future consideration
6
VOTE
Don't show the option to download videos in a shared KB
What is the challenge? Some customers with a private knowledge base do not want their users downloading videos. What is the impact? Allowing users to download content increases the likelihood that is shared with users who shouldn't have access to ...
0
Future consideration
8
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
6
VOTE
Display capacity line on Releases when looking at Epics board view
What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...
0
Future consideration
7
VOTE
Multi-language support in KBs
What is the challenge? Non-English speaking users need to access content in a KB. Currently a separate KB must be generated in each applicable language. How would you solve it? Provide KB translation. What impact would it make? Allow non-English s...
3
Future consideration
2
VOTE
Let reports nest feature to-dos within epic to-dos
What is the challenge? Users would like to see their to-dos grouped by parent epics and child features all together. Current, in the roadmap view, features won't nest under their parent epics. What is the impact? It is very difficult to see all th...
0
Future consideration