Skip to content
Documentation / 2 min read

Trackers

Connect Jira, GitHub Issues or Linear, check a real ticket, and attach the connection to the repositories that should use it. A tracker is never required. By the end, you will know how to distinguish a saved connection from one that has been checked.

Jira

  1. Save the connection

    Open Settings, then Tracker. Add the domain, email and token for Jira and save.

    What you see: The saved connection card offers a ticket check.

  2. Check a ticket

    Choose linked projects from Jira and check a ticket key you can access.

    What you see: Connected on success, or the driver’s refusal with its reason.

  3. Attach it to your repositories

    After the save or a passing check, Drover offers Use this tracker for your repositories, with every repository that has no tracker checked and a project picker for each. Choose Attach.

    What you see: Each attached repository takes its tickets from this Jira site. A repository you leave unchecked stays as it was.

GitHub Issues

  1. Save and check an issue

    Choose GitHub Issues when the installed driver offers it. Enter the declared connection fields and repository scope, save, then check an issue number on the saved card.

    What you see: Connected on success, or the driver’s refusal. Search accepts a full owner/repository#number query and identifies the source repository.

  2. Attach it to your repositories

    After the save or a passing check, choose Attach under Use this tracker for your repositories. GitHub Issues selects by connection, so there is no project picker.

    What you see: The attached repository lists under the connection card.

Linear

  1. Save and check a ticket

    Choose Linear when offered. Enter the declared fields, workspace and team, save, then check a ticket.

    What you see: Connected on success, or the driver’s refusal. Results identify their workspace and team, or the team for repository results.

  2. Attach it to your repositories

    After the save or a passing check, choose Attach under Use this tracker for your repositories. Linear selects by workspace and team, so there is no project picker.

    What you see: The attached repository lists under the connection card.

Credentials and availability

Secrets are stored in the system keyring, not in the published configuration. The app does not return saved tokens to the window. Connection scopes stay in shared settings.

An older driver without tracker setup support offers only Jira. Unsupported search, intake or closeout capabilities appear as explanatory text. A failed connection shows its own reason while results from other connections remain available.