Views:
Trend Vision One™ – Cloud Risk Management integrates with Jira. This includes Jira on-premises as long as the server is accessible via the Internet. If you use Jira in your business workflow, you can manually create tickets or configure triggers for automatic ticket creation to address corresponding vulnerabilities detected in your cloud account. The Jira ticket is automatically closed when you resolve a vulnerability.
Misconfiguration and Compliance allows the creation of issues in Jira. Notification settings for issues created in Jira can be configured within Jira. Open Notification schemes in Jira and configure as many users and groups as you want for newly created issues. See the Jira documentation on creating a notification scheme in Jira Cloud and Jira on-premises.
Note
Note
Be aware of ticket transition limitations. For a smooth ticket transition, ensure that:
  • The Jira workflow contains an OPEN status and a CLOSED status.
  • The workflow allows for a transition to CLOSED from any status.
  • No additional fields must be required during transition to the CLOSED status.

Set up a Jira channel

  1. Click Create a Jira channel.
  2. Set automatic notifications.
  3. Set manual notifications.
  4. Specify a Channel Name to distinguish the channel from others of the same type
    Note
    Note
    Channel Names are limited to 20 characters .
  5. Configure Triggers.
  6. Click Configure board now to set up your Jira notifications.
  7. Connect to Jira using the recommended OAuth Settings Setup or the Username and API Token Setup.
    1. To connect using the recommended OAuth Settings Setup, specify your Jira URL and click Connect
      Note
      Note
      Please ensure that you have set up your Jira client to use OAuth.
    2. To connect to Jira using the Username and API Token Setup, specify the following details:
      1. Jira URL
      2. Jira Username
      3. API Token
    3. On successful integration, the Misconfiguration and Compliance dashboard automatically loads the metadata from your Jira account. You can then specify the following extra settings to customize your communication channel:
      1. Project
      2. Assignee
      3. Issue Type
      4. Priority
      5. Custom Fields: To view the supported custom fields, select the Issue Type first and then click Reload Custom Fields.
        Misconfiguration and Compliance currently supports the following Custom Fields:
        • Radio buttons
        • Epics
        • Single line text
        • Number
  8. Copy communication settings.
**I*If the integration is connecting to Jira but not to the project, it could be because of the custom Jira project fields that are not yet supported. In such cases, we recommend creating a new project without custom fields.

Frequently asked questions

What Jira permissions does Misconfiguration and compliance require for integration?
The following permissions are required for integration:
  1. Project permissions: To browse projects
  2. Issue permissions: To create, close resolve, or delete issues
  3. Comment permissions: To add comments
I have custom project fields in Jira. Why is the Jira integration not working?
If the integration is connecting to Jira but not to the project, the project could have custom Jira project fields that are not yet supported. In such cases, create a new project without custom fields to connect to.