Integrations & automation — found from sitemap — Thoropass

Cited by

Facts read from this source

• Automations definition Report an error

  “An Automation is made up of two things: A Project: the project you want to pull tickets from A Tag/Label: a label that identifies the specific subset of tickets within that project”

• Automations sources Report an error

  “Automations make it easy to define a specific group of tickets you want to track in Jira Cloud or Service Now.”

• Automations output Report an error

  “Together, these two inputs come together to create a new Evidence Collector. This collector will pull all of the tickets matching the automation rule for you and surface these at time of audit.”

• Automations purpose Report an error

  “Many of the compliance and security frameworks we support may require you to pull populations of tickets as evidence such as security incidents, data deletions, access tickets, and so on.”

• Automations setup Report an error

  “Complete one or more Jira or Service Now Connection(s) Click Automations. Select a Project from the dropdown, this is the Jira / Service Now project you want to connect. Select a Tag choose the label that identifies which tickets within that project should be included. Click Save.”

• Automations editing Report an error

  “Click the Edit icon Update the project or tag as needed Click Save to apply your changes.”

• Automations edit warning Report an error

  “Changing the project or tag on an existing Automation will update the ticket population it pulls in.”

• Jira troubleshooting Report an error

  “You may not have access to that Jira project. Reach out to your Jira admin to request access.”