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 ...
There was a recent change to the formatting of the backlog releases v. actual releases on the epic/feature boards. This is creating bad formatting for those of us using dark readers to help with eyesight/migraines. Please update the formatting so ...
Patrick Eslick
over 4 years ago
in Epics
0
Shipped
Integration developers need documentation for the fields in the notifications generated by a webhook event. There are multiple ID fields and other fields with similar names and non-intuitive functions. Developers are left to infer their purpose, a...
Doron Chosnek
over 4 years ago
in Integrations
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...
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