Create tickets

Requirements#

• The Growth or Scale plan.
• An owner or admin, or a member with the Engineering or Product & QA lens, to connect the task manager and choose where each project's tickets go.
• After that, anyone on the team can create tickets.

Supported task managers#

• Jira (Jira Cloud): tickets go to a project, as the issue type you choose (Bug, Task and so on).
• Linear: tickets go to a team.
• GitHub Issues: tickets go to a repository.
• Asana: tickets become tasks in a project.
• ClickUp: tickets become tasks in a list.

1. 1

   Connect your task manager

   Owners, admins, and Engineering or Product & QA members, in Settings → Integrations.

   Open Settings → Integrations, press Connect next to your tool and paste a token. Codeskop checks it with the tool and stores it encrypted; only the last four characters are ever shown again.

   Which token to create

   • Jira: an Atlassian API token, plus your Jira site (for example https://acme.atlassian.net) and the email of the account that created the token. Tickets are created as that account.
   • Linear: a personal API key from Settings → Security & access → Personal API keys.
   • GitHub Issues: a fine-grained personal access token with Issues: read and write on the repositories you'll file to.
   • Asana: a personal access token from My settings → Apps → Developer apps.
   • ClickUp: your personal API token (it starts with pk_) from Settings → Apps.

   Use a shared account if you can

   Tickets are created as the person whose token you connect. A dedicated account for integrations (for example “Codeskop Bot”) makes it clear where tickets came from and keeps working when people leave.
2. 2

   Choose where each project's tickets go

   Still in Settings → Integrations, under Where tickets go, press Choose destination next to a project and pick the tool and destination: a Jira project and issue type, a Linear team, a GitHub repository, an Asana project or a ClickUp list. Each project has one destination; you can change it any time.

3. 3

   Create a ticket from an issue

   Open the issue and press Create ticket. The title starts as the issue's title; change it if you like, add an optional note, and press Create ticket. The ticket opens in a new tab, and the issue shows a link to it (for example Linear ENG-88) so nobody files it twice.

What goes into the ticket#

• Your note, if you added one.
• Summary: the issue, its kind and severity, environment, number of events and users affected, first and last seen.
• Exception or, for failing API calls, the request: endpoint, status and duration.
• Stack trace, with the frames in your own code marked.
• Where it happens: the top app versions, devices and OS versions.
• What the user did first: the screens, events and API calls just before the latest occurrence.
• A link back to the issue in Codeskop.

Jira gets a formatted description, Linear, GitHub and ClickUp get Markdown, and Asana gets rich text. Codeskop also adds a codeskop label in Jira and a tag in ClickUp where the project allows it.

Troubleshooting#

• “rejected the token”: the token expired, was revoked, or lacks access. Create a new one and reconnect.
• A destination is missing from the list: the connected account can't see it. Give that account access (for example, add it to the Jira project or Linear team) and choose again.
• Jira says a field is required: the project's issue type has extra required fields. Choose another issue type (such as Task or Bug) or make the field optional in Jira.
• “Choose where this project's tickets go first”: ask an owner or admin to set the project's destination in Settings → Integrations.

Next steps#