Currently it is not possible to add comments and send to project members at the release level. A classic example would be "I have updated the release date for this release to push back by a week". It is not appropriate to add this comment to a spe...
Comments should not be editable by anyone except the creator of the comment.
It does not seem right that anyone with access to our Aha environment should be able to edit someone else's comment. While notifications and history on the object may help identify when such a thing happens. But not having that ability to begin wi...
My users are getting bombed with update emails that don't make clear what has been updated. This is causing frustration, confusion, and mass un-subscribes to what should be important updates.
Would be good for emails regarding added comments to contain the release name (right now it contains the activity number (prefix-number). When you get “multiple people updated activity” or status change emails, it lists all the relevant info, but ...
Be able to generate status reports for various stakeholders that can be emailed. Would have: The status of work in progress What has been completed recently
Status of upcoming releases
Choose the frequency and audience
Integrate results from ...
New to-do's email notification improvement and settings
At this point new to-do's email notifications takes affect from general notification settings and user either gets lots of email or none until to-do's due reminder sends email notification.
Our need is that new to-do's should either always send em...
Creating the assignee of a feature/ initiative/ etc as a watcher
When assigning someone to a feature/ initiative/ etc, I would like Aha to automatically add that person to be a watcher so that they can receive notifications when any changes occur.
UPDATE: We would like all current and previous assignees to be...
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
The platform I manage has a wide range of stakeholders. Not every release is relevant to everyone one (some are internal). I would therefore like to restrict who gets what information so it des not confuse people. I am not sure that preventing the...