All ideas
Sort by:
Trending
Filter by:
Status
Showing 9002 of 9002
8
VOTE
Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.
As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...
0
Unlikely to implement
2
VOTE
Simplify adding existing Epics and Features to a User Story Map
When creating a new user story map, you usually add steps and then you might want to add existing records like Epics and Features under these steps. But adding an existing Epic or Feature from the "Add existing records" panel will just add those i...
0
Future consideration
4
VOTE
Show Requirement board like features & master features
On the board view, we currently have Master features and features but in some cases, there are enhancements scheduled at a story level (requirements). So like we can toggle between master features and features, if we can also view the requirements...
0
Future consideration
3
VOTE
Custom Tables information display
The custom fields that I have created in my custom table that appears in my Ideas Portal requires me to scroll horizontally for columns that are not spaced correctly. I recommend letting the information populate/appear vertically. See attached.
1
Unlikely to implement
2
VOTE
4
VOTE
Add features added in a story map to the bottom by default
Challenge When adding features in a story map, you usually add them top-to-bottom. if you later visit the feature board, the features will be in the opposite order -- the most recently added at the top, instead of the bottom. This feels very confu...
0
Future consideration
7
VOTE
Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)
I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...
3
Unlikely to implement
3
VOTE
Support epics with integration webhooks
Currently, integration webhooks are only available for Features and Releases. I would like to be able to integrate epics with integration webhooks so I can send epics to zapier, my own integrations, etc. At least enabling me to sidestep the poor s...
0
Future consideration
3
VOTE
Features show original release
After I ship a release and move features to a later release, I want to see what release my feature was supposed to ship in, so I can understand how well we are hitting our release targets so we can plan future releases better. It should be an edit...
0
Future consideration
6
VOTE
Ability to configure integrations not to create new records in Aha
In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA.
I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved