- How to think about integrating Aha! with your development tool (Jira, Azure DevOps, Rally)
- Manage your integrations
- Create multiple development tool integrations for a single Aha! workspace
- Integrate one Aha! workspace with multiple third-party systems
- Integrate Aha! with your calendar application
- Allow list IP addresses for on-premises development tools
- Manually send Aha! records to development tools
- Integrate Aha! with Azure DevOps Services or Azure DevOps Server (integrations 2.0)
- Sync sprints between Aha! and Azure DevOps (integrations 2.0)
- Integration guides (integrations 2.0)
- Azure DevOps Services Error: "Configuration error for 'installed': getaddrinfo: Name or service not known"
- Integrate Aha! with Azure DevOps Services or Azure DevOps Server (version 1.0)
- Integrate Aha! with Jira (integrations 2.0)
- Recommended Jira mappings
- Use the Jira integration through a web proxy
- Integrate with Jira next-gen projects
- Integration guides (integrations 2.0)
- Sync sprints between Aha! and Jira (integrations 2.0)
- Integrate Aha! with Jira Server on-premises (integrations 2.0)
- Track capacity between Aha! and Jira (integrations 2.0)
- Using webhooks for Jira integrations
- Troubleshoot Jira configuration issues
- Troubleshoot Jira error messages
- When multiple webhooks are needed and why
- Integrate a single Aha! product with multiple Jira projects
- Integrate Aha! with Jira (version 1.0)
- Map records between Aha! and Jira Core
- Duplicate records in Aha! after sending to Jira (integrations 2.0)
- Unable to establish “Links to” relationships with Jira
- Jira error: "Project with key ‘XXXX’ either does not exist or you do not have permission to create versions in it"
- JIRA error "Unhandled error: STATUS=500"
- Integration error: "Error: request to <url to server> took too long to respond"
- Feature status mapping is not inherited from integration configuration template
- Jira error: 401 authentication error with correct credentials
- Requirements do not change features when linked Jira issues are moved
- Jira error: 403 authentication errors
- User email matches, but assignee or reporter is not properly set in Jira
- Jira error: Remote error for 'installed': Unhandled error: STATUS=302
- Jira time-based estimates inflated from Aha! estimates
- Issues in Jira are linked to a fix version created in Aha! but are not getting pushed to Aha!
- Moving Aha! records to a new workspace broke the link to Jira issues
- Jira error: "Remote error for 'update_feature': Unhandled error: STATUS=404 BODY={"errorMessages":["No issue link type with name 'Relates' found."],"errors":{}}"
- Migrating Jira servers or changing Jira URL domain
- Jira warning: "Did not create new issue 'PROJECT_NAME-1234', no matching parent record found"
- Attachments from Aha! are being duplicated in Jira
- Double comments are added to Aha! from Jira
- Setting both original and remaining estimate is not supported in Jira legacy mode
- Jira error: "Data not accepted: assignee: User 'email@address.here' cannot be assigned issues"
- Jira error: "FixVersions: Version id '####' is not valid"
- Jira error: "Remote error for 'create_feature': Unhandled error: STATUS=404 BODY"
- Jira error: "Field 'FixVersions' cannot be set. It is not on the appropriate screen or unknown."
- Jira error: "Data not accepted: customfield_xxxxx: Field 'customfield_xxxxx" cannot be set. It is not on the appropriate screen or unknown."
- Jira error: "Remote error for ‘create_feature’. Integration needs to be reconfigured: issue types have changed, can’t find issue type
- Jira error: "Remote error for ‘create_feature’: Data not accepted: components: Component/s is required."
- Jira error: "Remote error for 'update_feature': Unhandled error: STATUS=404 BODY={"errorMessages":["Issue Does Not Exist"],"errors":{}}"
- Jira error: "Remote error for 'create_feature': Data not accepted: customfield_xxxxx: Operation value must be a string"
- Jira error: "Remote error for ‘create_feature’. Data not accepted: fixVersions: Version id ‘xxxxx’ is not valid."
- Jira error: "Event ‘installed’ failed due to an unhandled error"
- Jira error: "Remote error for ‘create_feature’. Data not accepted: summary: Field ‘xxxxxx’ cannot be set."
- Jira error: "Remote error for "create_feature': Data not accepted: <custom field>: <Custom field> name xxxxxx is not valid"
- Jira error: 401 authentication errors
- Jira integration allow list errors
- Jira error: "Remote error for 'installed': Unhandled error: STATUS=405"
- Updates in Jira are not reflected in Aha! records
- Jira field is not available in the integration mappings
- Import data from your development system (Jira, Rally, Azure DevOps, Asana, Github, Trello)
- Convert an integration from 1.0 to 2.0
- View integration log messages
- Moving records with Jira or Rally
- Map fields between Aha! and your development system (Jira, Rally, Azure DevOps, Asana, Github, Trello)
- Configure links between integrated records
- Link records in Aha! with existing records in another system
- Create an integration template
- Send changes and accept imports from another system
- Resync Aha! with your development tool
- Move a linked record to another Aha! product
- Map a single Aha! record type to multiple record types in your development system
- Send records in bulk to integrated tools
- Import error: "Record cannot be imported as a requirement because there is no valid relationship link to an Aha! feature"