Jira
Sort by:
Trending
Status:
Future consideration
Showing 174
9
VOTE
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...
0
Future consideration
8
VOTE
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...
1
Future consideration
1
VOTE
Ability to Integrate Ideas with Jira Service Desk
What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
0
Future consideration
9
VOTE
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...
1
Future consideration
3
VOTE
2
VOTE
Support of Embedding of Ideas in Confluence
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...
0
Future consideration
7
VOTE
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 ...
1
Future consideration
9
VOTE
Auto-sync of sprint field between JIRA and Aha
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...
2
Future consideration
2
VOTE
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...
0
Future consideration
8
VOTE
"Make everything OK" button on feature that triggers insert/update/delete/move JIRA->AHA
Hello, it would be very helpful if in scenario, where aha records are linked to dev tool records (e.g. JIRA), there would be a possibility to trigger full record update for a single record. Example: integrations config: Features linked to Epics in...
10
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved