Tickets in projectdocs

An imported ticket is a projectdocs entry of type ticket. Tickets always come from a provider. To record a bug or a request without one, create a bugreport or featurerequest entry, see Bug reports. You can anchor it to code, comment on it and find it from the code later. In the other direction, an entry you wrote becomes a new issue on the provider.

Import tickets as entries

1. In the projectdocs dashboard, click New entry in the toolbar (tooltip "Create a new entry in a phase").
2. Choose the type ticket. The ticket picker replaces the title field.
3. Choose the provider if more than one is configured.
4. Select one or more tickets in the list.
5. Click Create.

Tracemoor creates one entry per ticket. If an entry for a ticket already exists, it is refreshed instead of duplicated.

In the ticket picker:

• For Jira, the JQL field controls which tickets the provider returns. Click the run button or press Cmd+Enter (Windows/Linux: Ctrl+Enter). The query is saved for the exploration. See Set up ticket providers.
• The filter field above the list narrows the loaded list locally, for example auth or -88.

From the Tickets view you import a ticket with Create Entry, or several with Import to projectdocs.

What an imported entry contains

type: ticket
title: "PROJ-123: Login fails after token refresh"
ticket_key: "PROJ-123"
ticket_url: "https://acme.atlassian.net/browse/PROJ-123"
ticket_provider: jira
ticket_status: "In Progress"

The body is the ticket description as Markdown, followed by a link Open on jira ↗. ticket_provider is jira, github_issues or bitbucket_issues.

Importing a ticket again updates the title, the ticket fields and the ticket part of the body (from the heading down to the Open on … ↗ link) to the current state on the provider. Text below the link stays as it is. Write your own notes there, for example under a heading ## Notes.

In the projectdocs dashboard, an imported entry shows the provider, the key and the status. Open on Jira ↗ (or the provider's name) opens the ticket in the browser.

Create an issue from an entry

Use this to turn a bug report or a feature request you wrote into an issue in Jira or GitHub. Bitbucket cannot create issues.

1. Open the entry.
2. Choose File › Create Issue from Current Entry…. The dialog Create Issue from Entry opens. Summary and description are taken from the entry.
3. Optional: choose a Template. See Ticket templates.
4. Check Provider, Project and Issue type. The project defaults to the Jira project key of the exploration.
5. Optional: choose a Parent / Epic (optional).
6. Fill in the Required fields. They come from the Jira project configuration for the chosen issue type, with the allowed values as choices. Other fields are under Optional fields.
7. Click Create Issue.

Tracemoor writes the key and URL of the new issue into the entry's frontmatter. A later import of the same ticket refreshes this entry.

For GitHub, title and description are enough. There are no issue types or required fields.

Advanced: raw fields (JSON) takes fields that Jira knows but does not describe for the dialog, for example versions on some team-managed projects. The JSON is sent unchanged.

Translate before creating

Translate to English translates summary and description. Markdown is kept, English text stays unchanged. Revert restores the original text.

The menu next to the button chooses the translation provider:

Providers without a key are greyed out. The choice is saved as the new default. The default and the model per provider are also set in AI › Settings, General tab, Translation Provider. Without a choice, the first configured provider in the order OpenAI, OpenCode Zen, Anthropic, Ollama is used.

The dialog only creates issues. Status changes, comments and edits of existing issues are done in the Tickets view or by the AI.