-
Batch deleting of attachments
When attempting to delete a set of attachments, they have to be deleted one by one, each time confirming you do want to delete that attachment. If you have more than 2-3 it becomes very tedious and time-consuming to delete. It would be helpful to ...
0
Future consideration
-
Show progress on all features automatically
It's fantastic to be able to display progress (% complete) on features. Currently, you need to turn this on feature by feature. I would love the ability to make this visible on all features automatically.20 Likely to implement
-
Duplicate user story map
ability to duplicate a story map if want to show different versions- similar to duplicating features. goal of feature is to be able to work off different versions/drafts of the map.0
-
Ability to add custom fields onto the Task Form
Would like to add custom fields e.g Department Owner on the task form so we can create the reports we require.0
-
Ability to show 2 types of records in one column (master feature and feature records) but in different cells/rows in a Pivot report when the records are not linked.
In our configuration, we have either Epics(Features) or Master features linked to a Goal. In a pivot report, we want to show all Epics and Master Features linked to the Goal in one column. For the report, the primary record is the Goal and Epics ...6 Future consideration
-
Product Catalog
I would like AHA to have the ability to create a full product catalog that links roadmap items, marketing, pricing etc.. Currently, you can list work you are doing on your product for the future or something that you delivered but you cannot defin...1
-
StoryMap: I want to filter
I would like to filter e.g. for Initiative-related Features on a StoryMap - so filtering similar to Feature Board-filtering.0 Future consideration
-
Add Status / workflow to todos
I think todos have a lot of potential to represent non-feature work across Aha. I like the idea of not "polluting" aha with workarounds where features are used to represent work, nor requirements used to represent non-feature related work. There...0 Future consideration
-
Some ability to plan Project or Release with multiple features, cross-product
No description provided. -
Allow User Story Maps to Span more than one product
User Story maps should be able to show Master Features and Features from multiple products. We have complex products that have to work together in order to deliver usable solutions. Any step that the user does (install, configure, receive certain ...1 Future consideration