How to change issue links

You can link an issue to other issues to group issues with a common topic or indicate their dependency on each other. The number of links per issue is unlimited. The list of related issues is shown under the issue description.

Yandex Tracker has several link types:

Parent issue — Sub-issue
You can use this link type to decompose your issues. Break larger project chunks into standalone issues and sub-issues.
For example, let's assume you need to implement a new feature in your product, which implies resolving multiple smaller issues. For such cases, you can create a New feature parent issue and link sub-issues to it.
Related to
Use this link type to reference other issues with a common topic.
Depends on — Blocker to
Use this link type if a certain issue can only be worked on after another issue is completed. For example, the development of a new app feature can only begin after the interface was designed.
Duplicated by
Use this link type to group issues that describe the same task. For example, you should use this link if there are multiple Bug issues describing the same problem.
Epic for — Sub-epic
Use this link type to decompose issues if you are working with Scrum. How to organize issues into an epic
Original — Copy
This link is added automatically when you copy an issue with the Link issues after copying option. Copying an issue

You can also link issues to repository commits.

Issue links are created automatically when an issue key is entered into the issue description or comment body.

The queue owner can disable issue linking by a URL. To do this, select the Do not link to issues from other queues by a URL option in the queue settings.

To link one issue to another:

  1. Under the issue description, click Link to issue.

  2. To set a link type, click the name of the current type and select an option from the list.

  3. Select an issue to link:

    1. Select the queue where you want to create an issue.

    2. Give your issue a name and press Enter.

    If you can create an issue in the queue only using a form, you'll see the Select form button on the screen.

    You can also create a new issue by doing the following: in the upper-right corner of the page, select ActionsCreate related issue. Fill in the fields the same way as when creating a new issue.

    Select the Existing tab, specify the issue key or name, and then select an issue from the list. You can find the key on the issue page, above its title (for example, TEST-1234).

    Make sure that you have edit permissions for both issues.

To add a link to multiple issues, use bulk changes to issues.

Creating a sub-issue

You can break down your complex issues into simpler sub-issues and track their progress separately. After creating a sub-issue, you can change the link type.

  1. Go to the issue for which you want to add a sub-issue.

  2. In the upper-right corner, select ActionsAdd sub-issue.

    If you can create an issue in the queue only using a form, you'll see the Select form button on the screen.

  3. Fill in the fields the same way as when creating a new issue.

  4. Click Create issue. You will see a link to the parent issue at the top of the page above the sub-issue name.

To change an issue's link type:

  1. Open the page of one of the two related issues.

  2. In the Related issues list under the issue description, select the link for which you want to change the type.

  3. Next to the linked issue, click Change link type and choose a new type.

To unlink an issue:

  1. Open the page of one of the two related issues.

  2. In the Related issues list under the issue description, select the issue that you want to unlink.

    Make sure that you have edit permissions for both issues.

  3. Next to the linked issue, click Delete link.

Creating a sub-issue from an issue

You can make your issue a part of a larger (parent) issue using one of the two methods:

Under the issue description, click Link to issue and select Parent.

  • To create a new parent issue, select New, name the parent issue, and click Create.
  • To link an existing parent issue, select Existing, specify the parent issue's key or name, and select the issue from the list. You can find the key on the issue page, above its title (for example, TEST-1234).
  1. In the upper-right corner, select ActionsConvert to sub-issue.

  2. Specify the key or name of the parent issue, then select it from the list. You can find the key on the issue page, above its title (for example, TEST-1234).

  3. Click Save.

Changing the parent issue

To change the parent issue:

  1. Open the sub-issue page.

  2. In the Related issues list, next to the parent issue, click Change parent issue.

    • To create a new parent issue, select New, name the parent issue, and click Create.
    • To link an existing parent issue, select Existing, specify the parent issue's key or name, and select the issue from the list.

Removing the link to a parent issue

To remove the link to a parent issue:

  1. Open the sub-issue page.

  2. In the Related issues list, next to the parent issue, click Remove link.

Linking a commit to an issue

You can link a commit from a repository connected to Yandex Tracker to an issue: How to set up a repository.

To link a commit in the repository to an issue, specify the issue key in the commit comment. For example: Fixing error TEST-123.

You can view the linked commits:

  • In the Commits tab on the issue page.
  • On the queue commits page. To switch to the commits page from the queue page, click Commits in the top right corner.

List of related issues

If an issue has links configured, the list of related issues appears on the issue page. It is located under the issue description and the checklist, if one was created.

The list is shown as a table in which related issues are grouped by link type.

To open the list or any of the groups in a new window, point to the list or group name and click the icon that appears on the right.

You can customize the table with the list of related issues: sort the issues and select columns with issue parameters.

Customizing the list of related issues

You can add parameter columns to the table or remove unnecessary ones:

To save a filtered issue list to a file or copy it to your clipboard, click  Export in the top right corner and select your desired format. For more information, see Create a report from an issue list.

Several actions are also available inside the drop-down list. To see them, point to a parameter:

  • To read a brief description of the issue parameter, click .
  • To keep the selected parameter always at hand, click .
    The Pinned category will appear at the top of the drop-down list.
  • To change the order of the selected columns, drag them in the list by the icon.
  • To hide completed issues from the list, enable the Hide resolved issues option at the bottom of the drop-down list and click Apply.

Changing an issue parameter value or link type, or removing a link

You can edit the parameters displayed in the table cells.

  • To change the issue status or priority, a responsible user (for example, the assignee), or a date (for example, Deadline), click the current value and select a new one in the drop-down list.
  • To change the issue summary or another text field (for example, Story Points), point to it and click on the right.
  • To change the link type or remove a link, click on the right in the selected issue's row. In the submenu that appears, select Change link type and the type you need from the list, or Remove link.

Sorting the issue list

By default, the issue list is sorted by update date. To set a new sorting parameter (for example, by descending start date), use the button at the top of the page:

  • Click to change the sorting direction: descending or ascending.
  • To the right of the icon, click the name of the current sorting parameter and select a new one in the drop-down list.

You can quickly sort the list by a parameter from the table: point to a column and click the icon.

An issue key is a unique identifier contained in the issue link. It consists of the queue key and a number, for example TEST-123.