Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean
over 4 years ago
in Jira
1
Future consideration
Who would benefit? Users of both Aha and those who are not direct users of Aha on a daily basis but who relay on outputs from the platform. What impact would it have? It would simply data sharing and through Microsoft products such as Teams, Word,...
Guest
12 months ago
in Integrations
0
Future consideration
Update records on all integrations linked to a template at one time
We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...
Elaine Edwards
almost 5 years ago
in Rally
2
Future consideration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest
over 1 year ago
in Jira
0
Future consideration
We are trying to close the feedback loop for our customers. As product ideas come in through ZenDesk, they are kicked to Aha! and then the product team updates each ticket with a status. That status, while reflected in the ZenDesk issue detail, do...
Guest
almost 10 years ago
in Integrations
2
Future consideration
Ability to create a report of integration errors across multiple workspaces
Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko
over 3 years ago
in Jira
5
Future consideration
We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase
Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key t...
David Vins
about 6 years ago
in Jira
9
Future consideration
When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.
The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin
about 6 years ago
in Jira
5
Future consideration