Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
We use Assembla for issue tracking and Aha! for Roadmapping. Ideally the two products would be linked to tie roadmap features and milestones to Assembla.
Guest
over 10 years ago
in Wanted
13
Unlikely to implement
Add to the integration report if the "Based on Template" flag is checked or on the mappings page
We currently have over 200 active integrations. Knowing which ones are using the "Based on Template" flag is really useful when planning changes to the integration and ensuring that mappings are kept consistent amd not becoming unmanageable.
Andrew Brooks
almost 4 years ago
in Integrations
1
Likely to implement
There are many countries like in Middle East countries have different weekend days than Saturday & Sunday, therefore, it's very important to have the ability to change the weekend days for our planning & reports
Mohamed Al Dawy
about 6 years ago
in Wanted
1
Unlikely to implement
Improve the Idea Portal and Microsoft Teams Integration to include custom (And other) fields in the automatic post when a new idea is added
In the default integration for Microsoft Teams and the Idea Portal, I would like to customize the automated post when a new idea is submitted to include custom fields (e.g. category).
Evan Hollohan
over 2 years ago
in Integrations
2
Future consideration
Choose the product on the integration with Zendesk
When you have multiple products in Zendesk it would be nice of you could select the product to link to by default, or change the order of the products in the drop down list. This prevents mistakes are made by the support agents.
Jeroen Geerbex
about 10 years ago
in Integrations
4
Future consideration
Need full two way integration of a Story with VSTS
Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need:
1) any story delete in VSTS to be automatically deleted in Aha
2) any story added in VSTS to a Feature...
What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
CJ Jacobs
about 1 year ago
in Jira
0
Future consideration
Provide a warning explaining consequences when changing the workflow used in a workspace
When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...
Max Robbins
over 2 years ago
in Wanted
1
Will not implement
Convert story to epic in Jira when promoting requirement to feature
In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest
over 10 years ago
in Jira
2
Unlikely to implement