YouTrack Server 2024.2 Help


This workflow is used to automate common use cases that are relevant to a helpdesk project.






  • Copy to issue tracker (action)

  • Merge duplicate tickets (on-change)

  • Merge tickets manually (action)

  • Remind reporters and close pending tickets automatically (on-schedule)

  • Reopen ticket when reporter adds a comment (on-change)

  • Assign ticket to author of first reply (on-change)

  • New ticket from comment (action)

Use Case

This workflow provides extended functionality that is relevant to helpdesk projects.

When an agent encounters a ticket that should be handled by another department that isn't subject to the same time constraints and SLAs as a helpdesk, they can use the Copy to issue tracker action to create a copy of the ticket as an issue in another project. This comes in handy when, for example, the reporter submits a bug report or feature request that should be addressed by a development team.

When a helpdesk agent encounters a ticket that matches a support request that was previously submitted by the same reporter, they can mark one of the tickets as a duplicate. This helps to consolidate communication in a single thread and prevent agents from providing conflicting answers. Agents can either mark the ticket as a duplicate using the Duplicates link or by using the Merge ticket manually option in the action menu for the ticket.

Whichever agent adds the first public comment to a ticket is automatically set as its Assignee.

When an agent receives a reply from a reporter that should be handled as a separate support request, they can use the New ticket from comment action. This takes the comment text and copies it to the description field in the new ticket and prompts the agent to enter provide the summary.

When an agent has replied to a reporter in a ticket, they can move it to a Pending state to pause the SLA timer. This state indicates that the agent is waiting for the reporter to answer a question or confirm the action taken.

  • If the reporter doesn't reply within a specified timeframe, a reminder is sent to the reporter.

  • If the agent doesn't hear back from the reporter after a certain amount of time, the ticket is closed automatically. An additional message is sent to the reporter to inform them that the ticket was closed.

When a reporter adds a comment to a ticket that is set as Pending, it is reopened automatically. This helps to ensure that the resolution time is tracked according to the active SLA policy.


This workflow supports the following rules:



Copy to issue tracker

When an agent encounters a request that isn't meant to be handled according to the service level agreement that applies to tickets in the helpdesk project, they can use this action to create a copy of the ticket as an issue in a target project. They can then reply to the customer to provide a link to the new issue and close the support request.

When an agent selects this action in a ticket:

  • They are prompted to select the target project where the new issue will be created.

  • Once they confirm the selection of the target project, a copy of the ticket is created as an issue in the target project.

  • A link from the helpdesk ticket to the new issue is added automatically.

This action is only available to users who are granted an agent license in the current helpdesk projects. Standard users or agents from other helpdesk projects don't see this option in the list of available actions for the ticket.

Merge duplicate tickets

When a ticket is marked as a duplicate of another ticket, this on-change rule checks whether both tickets were reported by the same user.

  • If the tickets were reported by different people, an error message is shown to the agent and the operation is reverted.

  • When the same person reported both tickets, a public comment is posted in the ticket that is marked as a duplicate. The comment includes a link to the currently active ticket.

Merge tickets manually

This action rule lets an agent merge duplicate tickets using the merge with command. When an agent specifies this command, they are prompted to provide the ID of the ticket that want to merge with.

This action then applies the Duplicates link to the current ticket, which triggers the Merge duplicate tickets workflow rule described above.

Remind reporters and close pending tickets automatically

This on-schedule rule checks for tickets where the value for the State field are Pending.

  • If the ticket has been pending for more than 7 days, a reminder is sent to the reporter.

  • A second reminder is sent after 14 days.

  • If the ticket is still pending after 21 days, a comment is posted to the ticket and its state is set as Solved.

Reopen ticket when reporter adds a comment

This on-change rule automatically changes the value for the State field from Pending to Open whenever a comment is added by the reporter.

Assign ticket to author of first reply

This on-change rule automatically changes the value for the Assignee field to the agent who posts the first public comment in a ticket. This rule is only applied to unassigned tickets.

New ticket from comment

This action rule lets agents use the text from a comment in a ticket as the basis for reporting another ticket in the helpdesk project. The agent is prompted to provide a summary for the new ticket.

When this action is applied, a comment that references the new ticket is posted in the original ticket. A comment that contains a link to the original comment is also added to the new ticket.

Last modified: 11 June 2024