Legacy Documentation
You're viewing legacy documentation for API Fortress (deployed via an on-premises container). To view documentation for the new SaaS version of API Fortress — now known as Sauce Labs API Testing and Monitoring (with Sauce Connect tunnels) — see API Testing on the Sauce Labs Cloud.

Connectors – JIRA

API Fortress can absolutely integrate with your JIRA setup. However, because not all JIRA boards are created equal, if you would like a connector set up for your specific JIRA board please out to support@apifortress.com We will then gather the appropriate information and build you a custom connector for your JIRA setup.

Note: this connector does not come pre-loaded out of the box for self-hosted/on-premises, and will need to be loaded separately. To learn how to load the connector into your API Fortress instance click here.

If you are using the SaaS version there is a simple JIRA connector provided, below are the steps to configure it:

  1. Go to the settings page
  2. Click on “Alert Groups”
  3. Create a new group or add a connector to an existing alert group
  4. Add a new connector
  5. Choose the JIRA connector
  6. Configure the connector

    1. hostname – this is the host url of your JIRA instance
    2. username – username for your JIRA instance with permissions to create tickets
    3. password – password for the given username
    4. project_name – this is the project key of the project to send reports to
    5. issue_type – identifier of the issue type to be used, i.e. Task, Bug, etc

  7. Go into project settings for a project you would like JIRA alerts set up for

  8. Add the alert group that contains your JIRA connector to this project
The resulting ticket in JIRA will look something like this: