Jira
Sort by:
Trending
Status:
Future consideration
Showing 173
14
VOTE
The ability to review previously ignored integration candidates and undo the ignore
What is the challenge? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...
4
Future consideration
2
VOTE
Map custom release field in Jira integration
Currently the Jira integration doesn't allow users to map the custom release field, on records like features. We would like to be able to map this field and ideally to map it with a custom versions field in Jira. The two fields should be able to m...
0
Future consideration
176
VOTE
Dedicated Integration User
It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
16
Future consideration
1
VOTE
Add 'Send to integration' automation action for Aha! Ideas <> Jira integration
What is the challenge? As PMs review ideas submitted to Aha! there may be ideas that need to be sent directly to Jira — thinking about bugs that are reported through an ideas portal. What is the impact? Those ideas need to be reviewed alongside al...
0
Future consideration
29
VOTE
4
VOTE
Sync comments between Jira & Aha!
What is the challenge? Unable to Sync deleted and edited comments between Jira and Aha! What is the impact? Syncing deleted and edited comments between Jira and Aha! is crucial to maintaining accurate and up-to-date communication across teams. If ...
1
Future consideration
56
VOTE
Jira Integration of custom calculated field
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
3
Future consideration
1
VOTE
Aha Jira Integration mapping need to include the new Jira Object Capability
What is the challenge? Could not use the new Jira object in the mappings What is the impact? Teams want to group similar Epics in capability. without this, we can group them for tracking Describe your idea We already have Aha Integration to Jira i...
0
Future consideration
2
VOTE
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
0
Future consideration
4
VOTE
Record successful updates in Aha! from Jira "update records" action
What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved