Top level record Epic (Feature) is automatically imported from the Jira integration when a user story from a different previously integrated Epic is added
What is the challenge? We expect product managers to work the integration queue to import Epics (mapped to Aha! Features) from JIRA into Aha!, since Epics are the top level record in our mapped hierarchy. We do expect user stories (mapped to Aha! ...
In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes
about 5 years ago
in Features
0
Future consideration
Who would benefit? All users What impact would it make? More clarity for strategic open items How should it work? This has been raised and described in more detail under support request #919762, but the principle is that filtering out releases and...
Ben Bulow
about 2 years ago
in Roadmaps
0
Future consideration
Automation: Allow Automations for Release Phase and Release Phase To-Do objects
What is the challenge?
In order to track Release Checklists in Aha as to-dos by cross-functional team members needs automations to decrease amount of updates and auto assign appropriate owners.
What is the impact?
Cross-functional team mem...
Alex Berestenko
4 months ago
in Automations
0
Future consideration
When accepting a work request, provide the ability to filter the list of objects by the target workspace
What is the challenge?
When accepting a Work Request as an Epic object (for example), the user is prompted to select the Release to associate the Epic to. With approx. 100 workspaces and several releases per workspace, the list is unmanageable t...
Ryan Bradley
4 months ago
in To-dos
0
Future consideration
When embedding Aha Views into Meeting Notes, provide the ability for filtering the report view within the meeting notes
What is the challenge?
We have over 50 different review meetings within different areas of the organization. We would like to build standard roadmap, Approval, Tracking reports that can be filtered based on the meeting topic (generally tied to a...
Ryan Bradley
4 months ago
in Notes
1
Future consideration
What is the challenge?
Release notes draft is great, but need the JIRA ticket number so support teams can more quickly see what's been released
What is the impact?
Describe your idea
in the AI generated release notes include the inte...
Guest
4 months ago
in Releases
0
Future consideration
Add "For workspace" field for epic layout that reflects the release's workspace
What is the challenge? Users need to click into a release to see which workspace an epic's sits in. This is not very intuitive for new users and adds an unnecessary extra click to view a critical piece of information. Release has many definitions ...
Max Klin
8 months ago
in Epics
1
Future consideration
Option to include reference number in subject of email notifications
What is the challenge? For our users who transitioned from Jira to Aha, they are struggling with reduced efficiencies due to th efact that email notifications from Jira included the reference number in the subject while Aha only says "[AHA] Recent...
Support displaying images on cards on Now/Next/Later roadmap
What is the challenge? Cards that display on the Now/Next/Later roadmap are customizable, similar to the Features board, but they do not support include images at this time. What is the impact? Teams that use images to quickly differentiate work o...
Maria Plotkina
over 1 year ago
in Roadmaps
1
Future consideration