Please remove deactivated users from the Product -> Users Tab
When we remove users form the Aha system, I simply remove their seat. This is based on previous guidance and best practice guidelines.
When I navigate to the Product -> User tab, it looks like I have more people that have access to the Product ...
Let an initiative have prefix-## as items/epics have as well.
In our organization, people quickly adopted the prefix-## scheme when talking about items, ideas or epics. They are more easy to memorize than titles that might change over time. This is missing for initiatives, especially when copying the link wh...
Christoph Zehentner
about 7 years ago
in Strategy
0
Shipped
Change 'Summary' to '<Record type> name' when adding new records
The term 'Summary' is used when asking for the name of the record that is being created. 'Summary' is confusing especially since there is also a 'Description' text area.
When I create a release the modal says 'Release name' but for Ideas, Master F...
Sarah Cottle
over 7 years ago
in Application
0
Shipped
Firstly, thanks very much for all the improvements on models. I provided some input to these changes, and we started using them the day they were released. Thanks again.
Small improvement - Make the space on the left collapsible where the list of...
Add integration from Aha field to Preliminary Estimate field in Rally
I would like to fill out a T-shirt size estimate in Aha, and when I send to the Rally integration I'd like it to populate in the Preliminary Estimate field. Currently I do not have that ability in my integration mappings.
We have relabelled "Master Feature" to be "Feature" and "Feature" to be "Epic". When viewing a our Feature, it says "Calculated from Features" when it should say "Calculated from Epics". It even says "Epics right underneath it, but not for the lin...
Project Parker
over 7 years ago
in Epics
0
Shipped
As a user, I want to remove the logo from a Competitor.
Current implementation only supports a workaround of deleting the entire competitor and re-generating a new one. This is not ideal.
I have created a custom field in Aha which maps directly a field in Jira. I have created a pre-defined choice list in Aha! which contains all possible values in Aha!. When creating the integration between Jira and Aha! I have to manually match eac...