Tickets
In Tracemoor a ticket is a projectdocs entry of type ticket. It lives
in the exploration like any other entry, can be searched, commented and
anchored to code symbols. When you later work on an anchored function, the
ticket shows up from the code side. See
Anchors.
A ticket system is optional. Without one, the AI can still create ticket
entries in the projectdocs, and you can describe work in featurerequest or
bugreport entries.
Ticket providers
A ticket provider connects an external ticket system. Tracemoor supports three:
| Provider | Configured by | Import | Tickets view | Create, comment, transition, assign |
|---|---|---|---|---|
| Jira Cloud | Jira account in Preferences, project key per exploration | yes | yes | yes |
| GitHub Issues | GitHub remote of the repository and a GitHub token | yes | yes | yes |
| Bitbucket Issues | Bitbucket remote and an Atlassian / Bitbucket token | yes | no | no |
Jira Server and Data Center are not supported. Which providers are available depends on the configuration only. There is nothing to switch on. See Set up ticket providers.
Two directions
- Import: a ticket from the provider becomes a
ticketentry. Key, URL, provider and status go into the frontmatter, the description becomes the body. See Tickets in projectdocs. - Create: an existing entry, for example a bug report you wrote while exploring, becomes a new issue in Jira or GitHub. Key and URL are written back into the entry. See Create an issue from an entry.
flowchart LR
P["Jira / GitHub / Bitbucket"] -- "import" --> E["projectdocs entry\ntype: ticket"]
E -- "create issue" --> P
E -. "anchor" .-> C["code symbol"]
Where you work with tickets
| Place | Use |
|---|---|
| Tickets view | List, read and edit the tickets of a provider: status, assignee, comments, bulk actions. |
| projectdocs dashboard | Import tickets as entries, open the ticket on the provider. |
| File › Create Issue from Current Entry… | Turn the open entry into a new issue. |
| Chat | The AI reads, creates and updates tickets with the tickets_* tools. See Tickets and the AI. |
| Work packages | Group tickets under a parent and develop them on one branch. |
Company rules for the content of new issues are kept in ticket templates.