So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
Guest
almost 5 years ago
in Jira
0
Future consideration
When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration
I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA. I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required. When I perform an import from developmen...
Justin Woods
almost 5 years ago
in Jira
2
Future consideration
We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis
about 5 years ago
in Jira
1
Future consideration
Currently I use the feature board loads - organise all my features into releases with certain priorities and I use capacity planning and it's great. And I have a JIRA integration so anything I create in Aha is pushed out to JIRA with the correct r...
Guest
about 5 years ago
in Jira
1
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
about 5 years ago
in Jira
2
Future consideration
Sync with Jira include ability to link back to Aha Item
When configuring sync between Aha and Jira, it should include the ability to have a URL back to the associated Aha idea inserted in Jira field. This would allow Product and Engineering a better way to trace stories back to the original Features, O...
Joe Watson
about 5 years ago
in Jira
2
Future consideration
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
about 5 years ago
in Jira
1
Future consideration
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
Daniel Hirschberg
about 5 years ago
in Jira
0
Future consideration
Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release
Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor
about 5 years ago
in Jira
0
Already exists
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...