BigAgile's true power is unleashed when it is integrated with your teams' tooling. To allow the utmost flexibility, BigAgile can integrate with both Jira and AzureDevops whether they are hosted in the cloud or on-premise. You can have as many connections as you need, and you can integrate with both Jira and AzDo in the same BigAgile instance.

This article documents what needs to be done in Jira and Azdo to enable this integration.

Whether you're integrating with Jira or Azdo, BigAgile will need HTTPS access to the REST API. This can be done in a number of ways, including a secure VPN if your tooling is hosted on-premise.

For both Jira and Azdo, BigAgile will require a user with access to the required Projects. Whilst Read-Only permissions will allow some functionality, Read/Write permissions are recommended for the best experience.

BigAgile will need an API key generated for the user.

BigAgile will need a Personal Access Token (PAT) generated for the user.

Where a PAT is unable to be generated (older versions of Jira), BigAgile can connect using basic authentication, for which we will required a username and password.

BigAgile will need a Personal Access Token (PAT) generated for the user.

If you have any questions about the above, please reach out to support@bigagile.io