Jira
Sort by:
Trending
Status:
Will not implement
Showing 266
3
VOTE
Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to
What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
0
Likely to implement
96
VOTE
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
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
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Planning to implement
1
VOTE
175
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
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
1
VOTE
Raise authentication errors from the update configuration process to the integration log
What is the challenge? Authentication issues are not called out when they occur during the reload configuration process. What is the impact? The user thinks they have successfully reloaded the configuration from Jira but the authentication may fai...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved