We would like to be able to track Github issues by the initiative they relate to. We have the initiative information in Aha! but there is no way currently to get this information into Github. It would be very nice to have the initiate attached as ...
Add functionality to "release phase" categorization of features
In hardware projects, there are a lot of deliverables leading up to a release. I've been using features for all deliverables, regardless of whether they are "features" in the strictest sense and using feature types to define/sort. Using features r...
Eva Humphrey
almost 10 years ago
in Features
3
Shipped
As a Product Manager I have the need to calculate the release cycle time for our initiatives. I tried using the calculated columns feature however Release start date is not allowed to be part of the datediff function. Is that something we need to ...
When looking at the initiative it would be extremely helpful if the initiative had the value of Assignee in the user story section. NOTE: I created a mock of the wish
I understand we can create a report but sometimes it is easier to you an Initi...
When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements
We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.
Current: Today, you have to copy a document share link and paste it to others so they can collaborate with you. Idea: It would be great if I can add email addressed directly from the document's sharing functionality and invite those specific peopl...
When an idea is submitted, an email is generated and sent to the submitter. Email would be customizable by Aha! user/admin. Good add to product, because user is confirmed that Idea is submitted to idea portal, which brings more confidence to users...
Guest
almost 10 years ago
in Ideas portal
2
Shipped
Summary: Comments cannot be easily referenced because they are not numbered so if an update must be made, it's confusing and requires one to read through the entire thread. It would be better if an update can be made to the comment that's owned by...
When you're bulk editing across products, you cannot bulk edit custom field selections -- even if the products you're editing against are in the same product line and are inheriting the same custom fields. The custom fields are only bulk editable ...
Currently it's not possible to see which features are assigned to which user except by:
Filtering the Feature Board by assigned user
Going into each card one-by-one
This makes it hard to have a quick overview of who is responsible for what, or w...