For the development process

Applicable to Scrum, KanBan, software development, and hardware development projects, it allows custom allocation and task flow based on sprints and development processes.

When the subtask of a {User Story} are all completed, Modify its status to {QA} and notify the {QA Lead}

Trigger
Conditions
Actions

All Subtasks are done

Add Fields Conditions - Work Type - Equal to - Story

Modify Fields - Modify Status - In QA(Story) & Personal Notification Notification Channel: In-site /Slack/Email Recipients: {username}

When a new {User Story} is created, add it to the sprint {August}

Trigger
Conditions
Actions

Create Work

Add Fields Conditions - Work Type - Equal to - Story

Modify Fields - Modify Sprint - {Spring name}

When the status of a {User Story} is modified to {Released}, Mark all its subtasks as completed

Trigger
Conditions
Actions

Field Update - Modify Status

Add Fields Conditions - Status - From... To... - From: Any - To: Released(Story)

Complete all Subtask

When a {story} is associated with an epic, add the {Product Owner} as the follower

Trigger
Conditions
Actions

Field Update - Modify Epic

Add Fields Conditions - Work Type - Equal to - Story & Add Fields Conditions - Epic

- Equal to - {Epic name}

Personal Notification - Notification Channel: In-site /Slack/Email - Recipients: {username}

When the status of a {User Story} is modified to {QA}, assign it to {QA lead}

Trigger
Conditions
Actions

Field Update - Modify Status

Add Fields Conditions - Status - From... To... - From: Any - To: In QA(Story)

Modify Fields - Modify Assignee - {username}

When a {User Story} is created, add subtasks to it

Trigger
Conditions
Actions

Create Work

Add Fields Conditions - Work Type - Equal to - Story

Add Subtasks - Add Subtask

  • {Subtask 1} - Assignee - Due Time

  • {Subtask 2} - Assignee - Due Time

When the scope of the {sprint} is modified, notify the {sprint owner}

Trigger
Conditions
Actions

Field Update - Modify Sprint

/

Modify Fields - Modify Assignee - {username}

When a {User Story} is removed from the sprint, notify the subtask assignee(s)

Trigger
Conditions
Actions

Field Update - Modify Sprint

Add Sprint Conditions - Sprint

- From... To... - From: Any - To: None & Objects: Subtask All subtask satisfy conditions... - Status - Equal to - To Do

Personal Notification - Notification Channel: In-site /Slack/Email - Recipients: Assignee

When the estimated point of a {User Story} is over {13}, notify the {product owner}

Trigger
Conditions
Actions

Field Update - Modify Estimated Point

Add Fields Conditions - Estimated Point - Greater than - 13

Complete all Subtask

Last updated