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
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet
over 5 years ago
in Jira
1
Future consideration
When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest
almost 2 years ago
in Jira
0
Future consideration
When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA
Hi All,
We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
Guest
over 8 years ago
in Ideas / Jira
4
Unlikely to implement
As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar
over 1 year ago
in Jira
0
Future consideration
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Flag Feature/Story as had been deleted from integration
While I understand the desire to never delete a feature or story either in Aha or the integration partner (Jira in my case). I would like to see a feature that flags the deleted item in Aha as being removed. This would allow me to manually review ...
Kenny Burnham
over 4 years ago
in Jira
1
Future consideration
Copy integration mappings for records at the same hierarchy level
When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush
over 1 year ago
in Jira
0
Future consideration
We implemented the sprint field mapping and have found that the sync isn't quite automatic.
When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confus...
Guest
almost 6 years ago
in Jira
2
Future consideration