Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
almost 3 years ago
in Jira
0
Future consideration
Ability to see more than the last 200 logs in Aha-Jira Integrations
Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
Guest
over 4 years ago
in Jira
2
Future consideration
Synch story point estimates between Zenhub and Aha Epics (features)
We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
Guest
about 5 years ago
in GitHub
4
Future consideration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
Austin Merritt
over 6 years ago
in Asana / Integrations
4
Future consideration
What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
Don't Allow Jira Integration to Fail Based on One Field
What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...
Tags should propagate bidirectionally into Pivotal Tracker
Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Jason Novek
about 9 years ago
in Pivotal Tracker
2
Will not implement
When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest
about 9 years ago
in Jira
8
Unlikely to implement
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...