Solutions to common issues with the JIRA adapter:
- I just installed the Orchestrate JIRA adapter and made a commit against a JIRA ticket but the
association doesn't appear.
- Orchestrate is an event system that associates activities across systems. If the JIRA issue
you made a commit against hasn't been modified since installing the Orchestrate JIRA adapter,
Orchestrate is unaware of the given issue and therefore won't process an association to it.
The solution is to make a nominal change to the JIRA issue. This will automatically register
the issue with Orchestrate and associations will start happening after that.
- Associations were working fine but now stopped working or appearing in JIRA.
- First, test the connection from the JIRA project to the TeamForge project. In JIRA:
- If you receive an error, make sure that the credentials used to map the JIRA project to the TeamForge
project are still valid. TeamForge credentials can expire, user can be disabled or removed,
which would invalidate the integration. The solution is to update the credentials in JIRA and
re-test the configuration.
- "Test Configuration" fails with authentication errors
- Try the following troubleshooting steps:
- Check the username and password supplied. Note that this is a TeamForge username and password.
- Check that the Project Home URL is correct and is the intended Project Home URL.
- Check that the user supplied has proper permissions for the TeamForge project in question. The user whose
credentials are supplied must have API permissions in both TeamForge and Orchestrate, or is a project admin.
- I just re-mapped a JIRA project to a different TeamForge project and made a commit against a JIRA
ticket but the association doesn't appear.
- Orchestrate is an event system that associates activities across systems. If the JIRA issue
you made a commit against hasn't been modified since re-mapping the JIRA project to another TeamForge project,
Orchestrate is unaware of the given issue and therefore won't process an association to it.
The solution is to make a nominal change to the JIRA issue. This will automatically register
the issue with Orchestrate and associations will start happening after that.
- I get an error trying to re-map a JIRA project to a different TeamForge project
- Check that the user supplied has proper permissions in both the original and re-mapped TeamForge projects.
It is not sufficient for the user to have permission in just one of the two TeamForge projects in
question as the re-mapping process touches endpoints in both projects.