Features
Sort by:
Trending
Status:
Future consideration
Showing 1169
16
VOTE
Option to pull All comments or only comments after integration
As a developer it helps to see additional details and comments left by our operations so we can more fully understand what is going on with the ticket. Some times pertinent information is left there as opposed to putting the into the description, ...
5
Future consideration
2
VOTE
Group Level integration in Aha.
Who would benefit? All the teams who are using aha and Gitlab setup for their SAFe ways of working What impact would it make? Streamlined and logical grouping of features which are created in aha and synced to Gitlab How should it work? Group leve...
0
Future consideration
18
VOTE
Features Workflow by Status by Product
As a Product Manager, I would like a Kanban view of features by product. The current features workflow has swimlanes for assignees and sometimes that's good, but I often need to see features by product without regard to who they are assigned to.
3
Future consideration
11
VOTE
Small link for custom URL fields in feature cards
Presently you can add a custom URL field to the custom layout of a feature card, but it displays the entire URL. It would be nice to show the name of the field or even a simple link icon that I can click to open the URL in a new tab.
1
Future consideration
9
VOTE
Add "release phase" as an updatable field on the feature card.
I'm using release phase as my "sprints". When creating features, sometimes I want to add them directly into the sprint as they are being created. Right now it is a bit arduous to not have that field at my finger tips when creating features with th...
4
Future consideration
19
VOTE
Ability to customize the list of requirements within a feature
Currently, the list of requirements within a feature is fixed and only contains 3 columns:
Requirement #
Requirement Name
Status
It would be great if we could customize the columns to display. In my case, the status is not that important to see ...
7
Future consideration
1
VOTE
Create "Requirement Field" as new custom field type
Who would benefit? Any company that creates platform products What impact would it make? It would allow to connect items across workspaces that belong to difference levels. In our case we can use it to determine the influence of a feature or a req...
0
Future consideration
9
VOTE
Display Acceptance Criteria below description
When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved. We also need the acceptance criteria to sync to an equivalent...
1
Future consideration
1
VOTE
Ability to Configure Default View (Drawer / Details) for Records
Who would benefit? All Aha users What impact would it make? Provide consistent and optionable record viewing experience to users. How should it work?
Provide the Drawer and Details view options in personal setting per user preference on viewing ...
0
Future consideration
2
VOTE
Log work when importing completed records
My use case: I have existing epics in progress I want to import from Jira and I want to show accurate progress towards these epics based on story points completed. Here is the situation I am running: Create an epic in Jira, and 2 child stories und...
0
Future consideration