My ideas: Integrations
Sort by:
Trending
Status:
Shipped
Showing 946
65
VOTE
Add Rally "Project" field to integration reports
What is the challenge? What Project Name is an integration connecting to for Rally Integrations What is the impact? Cannot create a list report showing what Project Name is an integration connecting to in Rally Describe your idea Add the 'Project'...
0
Future consideration
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
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
42
VOTE
Rally Project name change should be reflecting in the Aha! Integration
What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...
1
Already exists
1
VOTE
Show more details in history when integrations/automations/extensions change data
There are many times when an integration, automation, or Develop extension will modify data on a record, but it's not always obvious how or why that data was modified: For integrations, all changes will be done as the integration user. It might no...
0
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
25
VOTE
Azure DevOps Integration - Sync dependencies at UserStories/Requirements level
What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
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
3
VOTE
Do not show an update to the record description in History when sending a record to an integration
What is the challenge? When you send a record to an integration, the history incorrectly indicates that there was an update to the description. What is the impact? This can cause confusion about what changes were actually made. It also impacts tho...
0
Likely to implement
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
© 2024 Aha! Labs Inc.•All rights reserved