Need to support the Jira code markup option.
If the developer enters sample code as part of the description in Jira, the description gets updated in Aha!
However the code markup is translated into very large tables in Aha!
At some point, Aha! upda...
Guest
over 8 years ago
in Jira
2
Future consideration
The importer shows all repository issues, including closed issues. It also doesn't show what the issue status is, so we must click through them to find those we want to import. I suggest: adding a status filter, set it to show open issues only sho...
Alexey Zimarev
7 months ago
in GitHub
0
Future consideration
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest
about 5 years ago
in Jira
0
Future consideration
Ability to set Aha field to a constant value as part of integration field mappings
My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
We are currently using the Aha.io and pivotal tracker integration to help seed our product roadmap into the engineering team's workflow. This has been great so far but the one biggest points of friction is trying to keep track of the features that...
Suzanne Vaughan
about 10 years ago
in Pivotal Tracker
4
Will not implement
Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories
I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!.
We'd much prefer that this not be the ca...
Doug Wilson
almost 5 years ago
in Jira
1
Future consideration
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
about 10 years ago
in Pivotal Tracker
2
Will not implement