All ideas
Sort by:
Trending
Filter by:
Status
Showing 9005 of 9005
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
8
VOTE
Allow inclusion of "parent workspace" fields (e.g., workspace name), in formulas for worksheet custom fields for Epics, Initiatives, Features, Ideas, Releases, etc.
All objects belong to a workspace, and sometimes there is a need to bring attributes of the workspace into worksheet custom fields, and in particular to display them in a report that has other object workspace fields already incorporated into the ...
0
Future consideration
8
VOTE
Allow automations to create calculated fields like reports
In reports one can create columns that are functions of other columns... this allow one to construct properties based on other variables assocaited with the object.For example I'd realy like to be able to set another custom variable based on the p...
0
Future consideration
3
VOTE
Automate feature creation on epics
Who would benefit? User teams that do a lot of repetitive work with contextual differences What impact would it make? It would help keep backlog items consistent and reduce the time needed for repetitive work created with necessary data relationsh...
0
Future consideration
27
VOTE
Kanban Board - Work-in-Progress (WIP) limit for status columns
Reference: https://en.wikipedia.org/wiki/Kanban_board
Work-in-progress (WIP) is a key design principle for Kanban. The ability to limit the number of items for each status column is part of the Kanban workflow. The limits per column should be use...
6
Unlikely to 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
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
25
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
Unlikely to implement
1
VOTE
6
VOTE
© 2024 Aha! Labs Inc.•All rights reserved