Update + Existing Features behavior on Releases Overview to be consistent with other Options for adding Features to this view
There are a couple of different ways of adding features to the Releases -> Overview/Roadmap views. The different approach have different behavior and the behavior for one of the methods is quite disruptive to the schedule. The scenarios apply w...
Allow turning off email notifications for submit-only ideas portal
My manager doesn't want to confuse users by sending them email from a totally different email address that has our company name attached to it. With the submit-only portal, would it be possible to turn off emails? I realize that users wouldn't be ...
When I create a new project, I start by creating an initiative then creating epics that are associated to the initiative. When I create features related to the epics, it does not inherit the association back to the initiative.
Fred Mahakian
almost 4 years ago
in Features
0
Shipped
Initiatives to have a human readable "ticket number"
Features have a human readable "ticket number", which is <Project Name>-#, where # is incremented for each new one created. It would be helpful for Initiatives to as well, so that you can tell someone easily to go to an Initiative, you could...
Release Roadmap Start On & Due On not working well with JIRA
We're using custom fields "Start Date" and "Planned Done Date" on our JIRA epics extensively, and we sync JIRA epics with Aha features. And we've added "Start Date" and "Planned Done Date" as custom fields in Aha features.
When we use the Releases...
Additional Automation Trigger for Idea creator and their domain
It would be great to see the option to review the email domain of the creator of an idea, so that we could update another field automatically. For example, the ideas created by users@customer.com the Customer field could automatically be updated t...
Christopher L
almost 4 years ago
in Ideas
0
Shipped
The current hierarchy is either too high, either too low for adequate product breakdown, and hence create difficulties in work assignment and follow up.
Initiative to Epic=ok, Feature to Feature, ADD User Story level in between, Reqs to Reqs=ok