Source: https://sprinto-test.docs-staging.pageloop.ai/data-library/access/dashboard-actions/manage-ticketing-systems

# Manage Ticketing Systems

Sprinto integrates with popular ticketing systems like **Jira**, **Asana**, and **Zendesk** to help route access-related violations and monitoring tasks to your internal workflows. You can configure one provider at a time and choose the specific projects to which access issues should be assigned.

This ensures visibility, accountability, and timely resolution of access-related risks.

---

### Select a ticketing provider

1. Go to **Data Library > Access > Critical systems**.
2. Click **Manage Ticketing System** on the top right.
3. Choose from the list of supported providers:
   - **Jira**
   - **Asana**
   - **Zendesk** and many more**.**
4. Click **Add** next to the desired provider.

Once selected, the provider is saved as the default and used across the Access section for pushing monitoring tasks and access violations.

> [!INFO]
>
> Only one provider can be active at a time.

---

### Add projects to track

After selecting a provider:

1. Click **Add Project**.
2. Select the desired project from the available list.
3. Click **Add Project** to confirm.

The project now appears in the active tracking list and becomes the destination for access-related tickets created by Sprinto.

---

### View and edit project settings

To view or edit a project’s tracking configuration:

1. Click the **settings (gear)** icon next to the project name.
2. You can:
   - **Set date filters** to limit visible tickets (e.g. from last 30 days).
   - **Add or edit tags** for better classification.
   - **Stop tracking** a project by clicking **Stop Tracking** and confirming.

Changes are saved immediately and will reflect in new monitoring tasks pushed by Sprinto.

---

### Change the provider

To switch to another provider:

1. Click **Manage Ticketing System**.
2. Select a different provider and click **Add**.
3. Repeat the project tracking setup steps for the new provider.

> [!WARNING]
>
> Existing tickets in the previous provider will not be migrated.

---

### Best practices

- Track only the projects actively used by your InfoSec or DevOps teams.
- Set clear ownership and tags to avoid misrouting of compliance issues.
- Periodically review tracked projects to retire unused ones.