This workflow defines state transitions and notifications based on the amount of time an issue spends in a specific state.
Name
@jetbrains/youtrack-workflow-time-management
Auto-attached
no
Rules
Define transitions for "State" field with predefined time constraints (state-machine)
Use Case
This workflow was originally taken from a submitted request (JT-6331).
The user who submitted this issue wanted to track issues reported by customers, prospects and team members and make sure issues are resolved within a specific time frame.
When a customer reports an issue:
The support engineers have one hour to acknowledge the issue.
The support engineers then have four hours to reproduce the case or to engage in a discussion to reproduce it:
If the issue is not reproduced within a day, then the support manager is involved and the sales department is notified.
After three days, the sales department organizes a customer visit to verify the issue on-site.
If the issue is classified as a bug, the issue is assigned to the R&D department.
Rules
This workflow supports the following rule:
Title
Description
Define transitions for "State" field with predefined time constraints
This state-machine rule defines the state transitions for issues in the project and determines the amount of time an issue can spend in each state.
The initial state is Submitted.
When the issue enters the Submitted state, the Subsystem field is set to Support. The support engineer is set as the Assignee.
From the Submitted state, the issue can transition to one of the following states:
If the state is unchanged after one hour, the state is automatically set to Overdue.
On event (action) reproducing, the state is set to Open.
On event (action) incomplete, the state is set to Incomplete.
When the state is set to Overdue, a notification is sent to the Assignee (if the issue is assigned), subsystem owner (if the owner of the Support subsystem is defined), or the project owner (if none of the previous conditions are true).
From the Overdue state, the issue can transition to one of the following states:
On event (action) reproducing the state is set to Open.
On event (action) incomplete the state is set to Incomplete.
From the Open state, the issue can transition to one of the following states:
If the state is unchanged after four hours, the state is automatically set to Wait for reproduce.
On event (action) approved the state is set to Approved.
On event (action) incomplete the state is set to Incomplete.
On event (action) can't reproduce the state is set to Can't Reproduce.
From the Wait for reproduce state, the issue can transition to one of the following states:
If the state is unchanged after one day, notification is sent to the owner of the Support subsystem (if defined) or the project owner.
If the state is unchanged after three days, a separate notification is sent to the owner of the Support subsystem (if defined) or the project owner.
On event (action) approved the state is set to Approved.
On event (action) incomplete the state is set to Incomplete.
On event (action) can't reproduce the state is set to Can't Reproduce.
When the state is set to Approved, the rule verifies that the Assignee is also set.
From the Approved state, the issue can transition to one of the following states:
On event (action) fixed the state is set to Fixed state.
On event (action) obsolete the state is set set (should transit) to Obsolete state.
From the Fixed state,the issue can transition to one of the following states:
On event (action) verify, the state is set to Verified state.
On event (action) reopen, the state is set to Open state.
From Can't Reproduce, Incomplete, Obsolete and Verified states, the issue can transition to the Open state upon action reopen.