PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox
over 4 years ago
in Jira
0
Future consideration
Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to
What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
Stephanie Lechner
11 months ago
in Jira
0
Likely to implement
Support updating JIRA Integration Links by csv upload
While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
Garret Duffy
over 2 years ago
in Jira
0
Future consideration
Pull Integration update on single linked Jira item
What is the challenge?
Need all fields updated from a Jira item, but the only current options are update all from Jira or "Resend all fields".
What is the impact?
Users have to manually go into each field in Jira they want to update, chang...
Jonathan Danielewicz
3 months ago
in Jira
0
Future consideration
Integrate Github projects not associated with a repository
Currently the Github integration forces us to select a repository in order to integrate with a project but we have the need to integrate with projects that are not associated with repositories.
Guest
11 months ago
in GitHub
2
Future consideration
Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei
over 3 years ago
in Asana
0
Future consideration
What is the challenge?
I would like access to TestRail results and Github information in Roadmaps
What is the impact?
Team members that don't have access to Aha Develop cannot see this data.
Describe your idea
Please allow extension ...
Devin C
3 months ago
in Integrations
0
Future consideration
What is the challenge? We have a Jira-Aha integration template that span across multiple Aha workspaces. When we change the integration template (add/remove fields for instance) we need to sync data between Jira and Aha to ensure both systems are ...
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
Karie Kelly
over 3 years ago
in Integrations
0
Future consideration