Skip to main content
Ticket Manager checks a ticket’s requirements, asks PR Author to implement the change, and keeps the ticket updated. Your team reviews and merges the change. Get started in three steps: connect your tools, set up with Advisor, and try a ticket in your tracker.

​
From ticket to PR

Human steps are highlighted.

​
1. Connect your tools

Connect your team’s code host and ticket tracker in Cosmos: Follow the connector guides to authorize access to the repository and tracker. You may need an administrator to complete the setup.

​
2. Set it up with Advisor

Open Cosmos Advisor from Home. Replace the placeholders and send:
Set up Ticket Manager for [ticket tracker] with code in [code host]. Show me how to delegate tickets.
Advisor helps configure:
  • The Experts: Ticket Manager and the PR or MR Author that implements changes.
  • The environment: access to your repository and the tools needed to build and test it.
  • The automation: which delegation event starts work.
For GitHub Issues or Jira, choose a delegation label with Advisor, such as cosmos-ticket-manager. Create it in your tracker if needed, and make sure the automation uses that exact label. Complete Advisor’s setup checks, approve activation when prompted, and confirm the automation is enabled before delegating a ticket.

​
3. Try it in your ticket tracker

Go to GitHub, Linear, or Jira and create a ticket in your usual project or repository. Start with a small text change so it’s easy to check the result:
Update the Save button text Change the settings page’s button label from “Save” to “Save changes”. Keep its behavior and styling unchanged.
Then delegate it:
Open the issue and add the delegation label you configured with Advisor.Ticket Manager removes the label after claiming the issue. This is expected; follow the ticket update rather than re-adding it.
Delegating a ticket starts real work: it can update the ticket, push code, and open a PR or MR.
Check the ticket for a status update and session link. If a specification needs approval, follow Review spec, answer the questions, and approve the scope in that session. Once the ticket is ready for implementation, the Author makes the change and links the PR or MR back to it.
Nothing started? Check Automations → Run History in Cosmos. Give Advisor the ticket and automation links and ask it to check the connection, trigger, and delegation event before making changes.