Skip to main content
Create Tickets for Basecamp

Create Basecamp tickets through Drata associated with risk, control, or test.

Updated over a month ago

Managing your security compliance can require coordination and collaboration with other members of your organization. Drata makes this easier by integrating with the tools you already use on a daily basis, including Basecamp. By connecting Basecamp to Drata with write access enabled, you can create and assign tickets for Controls (DCF and Custom), Tests, and Risk Management in Drata and have them accessible in your Basecamp account.

Before Diving In

  • Users with Admin, Information security leads, Workspace Admin access can create and view Basecamp tickets within Drata, however a user must have Admin access in order to set up or edit the Basecamp connection

  • 'Write Access' is already enabled when creating the initial Basecamp connection

Limitations / Watchouts

  • Tickets can be created in primary and secondary workspaces

Connecting Basecamp To Drata

  1. In your Connections page, search for and select Basecamp.

    • Ensure you are on the Available connections tab.

    • You can also utilize the filter by selecting Ticketing for the connection type.The slide-out panel will provide step-by-step instructions to set up the connection.

  2. Follow the instructions in the slide-out panel carefully and ensure that the required fields are entered.

Creating Basecamp Tickets via Drata

The places you can create a tickets is: Control Details, Test Details, or Risk Details (in Risk Management) drawer. If there are no tickets or tasks currently associated to a Control, Test, or Risk, you will be prompted to create one to get started.

Select Create ticket to create a Basecamp ticket

For the destination, if you have multiple ticketing systems connected to Drata, you may have to search and select Basecamp. The rest of the steps will depend on how you organized your Basecamp tickets. It may differ from the following sections.

After selecting a destination, select your project and then continue on to the ticket details section. The title and description will be auto-populated. Select Create ticket once you are completing the ticket details you’d like to input.

Viewing and Managing Tickets in Drata

When Basecamp tickets have been created for a specific Control, Test, or Risk (in Risk Management), they will display within the drawer. The most recently added ticket will display at the top of the list.

Each ticket listing includes the following information:

  • Ticket Summary / Short Description – as entered by the user

  • Date the ticket was created

  • Date the ticket was updated

  • Ticket Status – as reported by Basecamp

  • Name of Assignee – tickets can be assigned to any selectable Basecamp User. This user does not need to be a tech gov or admin in Drata.

  • Name of person who created the ticket

  • To view, edit, and manage a ticket, click the “Manage ticket” button and you'll be taken to Basecamp.

  • To download the ticket information, click on the save icon next to the trash bin. This will download a zip which will contain a pdf of the ticket details.

  • To unlink a ticket from the control, test, or risk, click the trash bin. Unlinking a ticket will not delete the ticket in your Basecamp account. Note: once a ticket is removed, it cannot be re-linked.

  • A maximum of three ‘In Progress’ tasks will display in the list in the drawer. To see all tickets associated with a particular Control, Test, or Risk (in Risk Management), click the ‘View all tasks’ link and a modal will open.

Here the tickets are divided into two standardized categories, 'In Progress' and 'Done':

  • In Progress – Tickets in any open state as defined in your Basecamp instance.

  • Done – Tickets in any completed state as defined in your Basecamp instance, i.e. Closed, Done, etc.

Only tickets created in Drata for that specific Control, Test, or Risk (in Risk Management) will display in Drata. Tickets created directly in Basecamp will not be pulled into the Drata application for ticket management.

Did this answer your question?