Skip to main content

Population Automation in Thoropass

Automated retrieval of populations through Jira & Service Now

J
Written by James Fletcher

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.
​

Doing this manually can be quite time consuming and error prone. Thoropass Automations solve this by letting you define exactly which tickets belong to a given audit population once, and then reliably surfacing that same group every time you need it, keeping your evidence collection consistent and your audits on track.

What are Automations?

Automations make it easy to define a specific group of tickets you want to track in Jira Cloud or Service Now. This eliminates the need for manual searching or filtering every time.
​

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

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.

Setting Up an Automation

  1. Complete one or more Jira or Service Now Connection(s)

  2. Click Automations.
    ​

  3. Select a Project from the dropdown, this is the Jira / Service Now project you want to connect.

  4. Select a Tag choose the label that identifies which tickets within that project should be included.

  5. Click Save. Your Automation will now create an Evidence Collector that will begin pulling in the matching ticket population.

Viewing your Automations

All of your saved Automations are listed in the Automations section. Each one displays the connected projects and tags

Editing an Automation

  1. Find the Automation you want to update in the list.

  2. Click the Edit icon

  3. Update the project or tag as needed

  4. Click Save to apply your changes.

⚠️ Note: Changing the project or tag on an existing Automation will update the ticket population it pulls in.

When Submitting an Automation

Please be sure to describe the automation in the box in the ER.
​

Troubleshooting

Q. My Automation isn't pulling in any tickets

A. Make sure the tag you selected is actually applied to tickets in the chosen project. If the tag exists but no tickets have it, the population will be empty.

Q. I can't find the project I need in the dropdown.
​A. You may not have access to that Jira project. Reach out to your Jira admin to request access.

Did this answer your question?