Start
Issue logging is straightforward and is accessible from several places in YouTrack:
- Issues New Issue button in top navigation. If you select issues in the issue list, the drop-down becomes available and allows linking the selected issues to the new issue.
- Dashboards New Issue button in top navigation.
- Agile boards Create -> Card… or Create -> Swimlane… from top navigation or New card… anywhere in the swimlanes. Issues created from an agile board will have some values default from the location selected or the previous issue created.
- Projects' dashboards' New Issue link in header. Issues created from a project have that project set.
No matter where you create an issue from, the fields to populate are the same, and are nearly identical presentation. Agile boards move the Project, and provide a much smaller area to work in.
Set Fields That Change Behaviour
There are a few fields that are very important to get correct. These should be set first:
- Project: Select the correct project for the issue. This is very important! Changing the project can change the set of fields for the issue. An incorrect project also makes it very difficult to track the issue and the project progress.
- Type: Select the type of issue. Changing the type can change the set of states and allowed state transitions.
Fill Out Issue
Fill out the rest of the issue fields. Notes on some fields:
- Summary is required. It should be a short phrase for description sufficient to give the gist of the issue when seen by itself.
- Description is strongly recommended. It should contain a complete explanation of the issue.
- Bug: Provide steps to reproduce, expected results, actual results. Images or links are encouraged.
- Task: Provide explanation of task.
- Story, Epic: Provide description of story, acceptance tests, mockups, etc.
- Priority: Set to Critical if it needs immediate attention. Set to Blocker if it would block release.
- State: Should be able to leave alone.
- Subsystem: Can be used to categorise the general area of the issue, for example if it affects database, backend, api, or frontend.
- Affected versions: Mostly for bugs. Select the version(s) the issue is found in.
- Fix versions: Indicates the version the issue is targeted to. Leave empty for bugs and the triage team will set it. Set to the release version for stories and tasks.
- Due date: If the issue has a deadline, enter it.
Create, Postpone, or Delete
To create the issue, click the Create button.
To postpone the issue and save it as a draft, click the Cancel button or navigate away from the page. This saves the state of the issue in your drafts list. You can access you drafts list by creating a new issue, and there will be a Drafts dropdown above the summary.
To discard the issue, click the Delete button.
