An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
about 10 years ago
in Jira
17
Future consideration
Development Integration -- Support rendering of images embedded in description field
Currently when you import from Jira or Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in...
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
over 2 years ago
in Jira
2
Future consideration
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira
over 1 year ago
in Jira
2
Future consideration
Zendesk integration supports custom layout on ideas
Is it possible to have a custom field visible on the zendesk create idea/link form? We are starting to using a custom tag field to help identify product components. It would greatly help if we could apply categories and custom field information wh...
Guest
almost 9 years ago
in Integrations
9
Future consideration
What is the challenge? Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! record...
Michael Bruner
9 months ago
in Integrations
0
Future consideration
Activity webhook configuration should account for nested workspace hierarchy
What is the challenge?
I have a workspace hierarchy like so:
Company line
workspace
workspace
Test line
test workspace
test workspace
I would like to build an activity webhook in the Company line and send data to a third party ...
Justin Waldorf
5 months ago
in Integrations
0
Future consideration
Slack integration for portal users to submit ideas
Currently only Aha! Users and Reviewers can add Ideas via Slack integration. Non-Users/Reviewers have always been able to submit ideas via the web portal so extending that as part of Slack -> Aha! seems like a next step.
Our users would like t...
Currently, users of the Salesforce <> Aha! integration can create / link 'Aha! Ideas' to 'Salesforce Opportunities'. Further those 'Aha! ideas' can be promoted to / linked with 'Aha! Features'.
As a user of the Salesforce <> Aha! inte...
Erick Crowell
about 9 years ago
in Salesforce
1
Future consideration