Each one of our features is linked to a designated release phase. We would like to be able to better view this on the features board by ranking features by the release phase. I have added the release phase to the custom cards for features-which is...
Dylan D'Erminio
almost 5 years ago
in Features
0
Future consideration
Add ability to customise the message that is shown to people that have not been provisioned a user in the account
When SSO is used and a user attempts to access the company aha instance, they are presented with a list of the emails of the people who have billing permissions (not sure if only when the account does not have available seats). Either way, compani...
Stefan Stefanov
almost 5 years ago
in Account settings
3
Future consideration
Update Jira integration when Jira custom fields were added
It looks like if you add a custom field in JIRA, Aha will not recognize it unless you delete the integration and add a new one, which means you need to relink everything.
You should be able to go through the integration UI and add new field mappi...
Christian Stark
over 7 years ago
in Jira
1
Already exists
We currently have no way for Rally to tell Aha that a feature is fully groomed. This would help considerably to give Product team visibility to the feature grooming status in AHA for PI Planning and priority alignment. Aha has a feature status of ...
Guest
over 7 years ago
in Features / Rally
0
Future consideration
It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...
Todd Materazzi
over 2 years ago
in Features
0
Future consideration
better validation warnings and units tips and handling on estimates fields
the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...
Kevin Martin
over 2 years ago
in Capacity planning
0
Future consideration
please let admin better control the field choices on apply rank to users cannot make bad choice
apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...
Kevin Martin
over 2 years ago
in Roadmaps
0
Future consideration
Enhance Trend report to include projected/forecasted line
This idea to suggest an enhancement the 'Trend' Report type to include an additional generated future trend line to forecast where the trend of existing data is headed. The screenshot below has a green dotted line to illustrate how the proposed fo...
Tom Bailey
over 7 years ago
in Reports
0
Unlikely to implement
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Aha! Develop: organize the program increment backlog into teams with a filter
The ideal workflow for a SAFe team is as follows: Define work (workspaces and teams): product and engineering define the work to be done Prioritize work (backlog management): work is groomed and assigned to the prioritized backlog Plan PIs (progra...
Dale Potter
over 2 years ago
in
0
Future consideration