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...
Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest
almost 11 years ago
in Pivotal Tracker
2
Will not implement
Deleting a feature or requirement should delete the linked Jira issue(s)
When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest
almost 11 years ago
in Jira
11
Will not implement
Who would benefit? anyone using Kanban and want's accurate process measurements What impact would it make? Better insights into the flow of work in your system, better forecasting of future work without having to ever ask for estimates that are mo...
Guest
over 1 year ago
in Wanted
0
Will not implement
If a comment is deleted in Jira, please delete that comment in Aha! also
Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes
about 7 years ago
in Jira
1
Will not implement
More complete field mapping between Aha! and FogBugz
Both products are feature rich and have many alignments which would be great to keep in sync.
Aha! Feature Type - FogBugz Case Category
FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest
almost 10 years ago
in Integrations
4
Will not implement
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Guest
almost 7 years ago
in Pivotal Tracker
1
Will not implement
Integrations 2.0: JIRA Default map Aha! URL to JIRA Aha! Reference field
1.0 did this; 2.0 does not.
As a user I have to manually add the mapping between the URL field for an Aha! record and the Aha! Reference field for the JIRA record.
For Releases we automatically map the URL to the description field.
For Features/...
Danny Archer
over 7 years ago
in Integrations
0
Will not implement
Ability to manually link features in Aha to existing Redmine items
As a Redmine user with many projects in flight, I want the ability to link a feature in Aha! with an existing Redmine feature so that I can manually create an integration between the two objects.
Nathaniel Collum
over 7 years ago
in Integrations
0
Will not implement