You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/automations/custom-automations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Automate project tasks with trigger based workflows
3
3
description: Automate repetitive project tasks with trigger-based workflows. Set up rules to automatically update work item properties, assign team members, and manage priorities when specific conditions are met.
Automations let you streamline your project management workflow by automatically performing actions based on specific triggers and conditions. This powerful feature eliminates repetitive manual tasks, ensures consistency in your processes, and helps your team maintain focus on high-value work by letting the system handle routine operations.
description: Automate repetitive project tasks in Plane.
4
+
---
5
+
6
+
# Automations
7
+
8
+
Automations handle repetitive project work so your team can focus on the work that matters. Plane offers two kinds of automations, both configured in **Project Settings → Automations**.
9
+
10
+
-**Built-in automations** are ready-to-use toggles for common housekeeping tasks — archiving closed work items, closing stale ones, and sending deadline reminders.
11
+
12
+
-**[Custom automations](/automations/custom-automations)** let you build your own trigger-condition-action workflows — like auto-assigning a reviewer when a work item moves to QA, or adding a label when priority changes.
Automatically archive work items that have been completed or cancelled, keeping your active views clean.
19
+
20
+
1. Navigate to **Project Settings → Automations**.
21
+
2. Toggle on **Auto-archive closed work items**.
22
+
3. Set the **Auto-archive work items that are closed for** duration. Options include 1 month, 3 months, 6 months, 9 months, 12 months, or a custom time range.
23
+
24
+
Once enabled, work items that have been in a completed or cancelled state for longer than the configured duration are archived automatically. Archived work items remain searchable and accessible in the project's archived view, but they no longer appear in active lists, boards, or spreadsheets.
25
+
26
+
## Auto-close work items
27
+
28
+
Automatically close work items that have been inactive — not completed or cancelled — after a period you define. This prevents stale work items from cluttering your project indefinitely.
29
+
30
+
1. Navigate to **Project Settings → Automations**.
31
+
2. Toggle on **Auto-close work items**.
32
+
3. Set the **Auto-close work items that are inactive for** duration — for example, 1 month.
33
+
4. Choose the **Auto-close status** — the state that inactive work items will be moved to (e.g., Cancelled).
34
+
35
+
Work items that haven't been updated within the configured period are automatically moved to the selected auto-close status. Only work items that are not already in a completed or cancelled state are affected.
36
+
37
+
## Auto-reminders
38
+
39
+
Send automatic reminders via email and in-app notifications to keep your team on track with deadlines. When a work item's due date is approaching, assignees receive a reminder so nothing slips through the cracks.
40
+
41
+
1. Navigate to **Project Settings → Automations**.
42
+
2. Toggle on **Auto-reminders**.
43
+
3. Set the **Send reminder before** timing — for example, 3 days before the due date.
44
+
45
+
Once enabled, assignees and work item subscribers receive both an email and an in-app notification at the configured interval before each work item's due date. Only work items with a due date and at least one assignee or subscriber trigger reminders.
Copy file name to clipboardExpand all lines: docs/core-concepts/cycles.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ Automate the creation and management of cycles according to predefined configura
132
132
133
133
1. Navigate to **Project Settings → Features → Cycles**.
134
134
2. Turn on the **Auto-schedule cycles** toggle and configure:
135
-
- Cycle Title — Set a naming convention for automatically created cycles.
135
+
- Cycle Title — Set a base name for automatically created cycles. Each cycle gets a numerical suffix appended automatically (e.g., if you set the title to "Sprint", cycles are created as "Sprint 1", "Sprint 2", "Sprint 3", and so on).
136
136
- Cycle Duration — Define the length of each cycle in weeks (e.g., 1 week, 2 weeks).
137
137
- Cooldown Period — Add an optional buffer between cycles in days for planning and retrospectives.
138
138
- Cycle starts day — Choose the start date for the first auto-scheduled cycle.
@@ -143,6 +143,7 @@ Once enabled, the system automatically:
143
143
144
144
- Generates the configured number of future cycles based on your settings.
145
145
- Creates a new cycle when the current one concludes to maintain the specified schedule.
146
+
- Numbers each new cycle sequentially, continuing from the last created cycle.
146
147
- Ensures cycles don't overlap and follow the defined cadence.
147
148
- Applies consistent naming conventions and durations across all cycles.
Copy file name to clipboardExpand all lines: docs/core-concepts/issues/display-options.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,18 +43,25 @@ Grouping helps you organize work items based on shared attributes, making it eas
43
43
- Created By
44
44
- Milestones
45
45
- Epics
46
+
- Releases
47
+
- Work Item Types
46
48
- None
47
49
48
50
## Sub-group by
49
51
50
52
You can further refine your view by adding a sub-grouping. For example, you could group by State and then sub-group by Assignees to see the state of tasks per team member. Sub-grouping options include:
|**Text**| Single line, Paragraph, Read-only | The **Read-only** attribute cannot be marked as mandatory. Enter text in the Read only data box for this option. |
101
-
|**Number**| Default value | An optional default value can be given to this property type. |
102
-
|**Dropdown**| Single select, Multi select, Add options | Specify the values for the dropdown under **Add options**. |
103
-
|**Boolean**| True/False | Default value is false. This attribute cannot be marked as mandatory. |
104
-
|**Date**| Date Format | Consistent date format across all properties. |
105
-
|**Member picker**| Single Select, Multi select | Displays a list of all project members. |
|**Text**| Single line, Paragraph, Read-only | The **Read-only** attribute cannot be marked as mandatory. Enter text in the Read only data box for this option. |
101
+
|**Number**| Default value | An optional default value can be given to this property type. |
102
+
|**Dropdown**| Single select, Multi select, Add options | Specify the values for the dropdown under **Add options**. |
103
+
|**Boolean**| True/False | Default value is false. This attribute cannot be marked as mandatory. |
104
+
|**Date**| Date Format | Consistent date format across all properties. |
105
+
|**Member picker**| Single Select, Multi select | Displays a list of all project members. Members selected via a member picker property are automatically added as subscribers to the work item, so they receive notifications for updates, comments, and status changes.|
106
106
107
107
### Examples of custom properties
108
108
@@ -121,6 +121,7 @@ Once the project Admin sets up the work item types any project member can use th
121
121
122
122
- In the **Create new work item** modal, the user can choose the desired work item type from the list at the top left corner. By default, the work item type `Issue` is selected displaying both system-defined and custom properties.
123
123
- Changing the work item type will update the modal to display the relevant properties for that type.
124
+
- When a member picker property is filled in, the selected members are automatically subscribed to the work item. This means reviewers, stakeholders, or anyone added through a member picker stay informed without needing to be manually subscribed.
124
125
- The system ensures that all properties marked as mandatory are filled before creating the work item.
125
126
126
127
@@ -154,6 +155,22 @@ You can change the work item types for several work items at once. Here’s how:
154
155
155
156
4. Click **Update** to apply the changes.
156
157
158
+
## Set the default work item type
159
+
160
+
The default work item type is pre-selected whenever someone creates a new work item. Initially this is set to the built-in `Issue` type, but you can change it to any active work item type.
161
+
162
+
1. Navigate to **Project Settings → Work item Types**.
163
+
2. Click the **…** menu next to the work item type you want to make the default.
164
+
3. Select **Set as default**.
165
+
166
+
The selected type now shows a **Default** badge and is automatically pre-selected in the Create new work item modal. You can change the default at any time by repeating these steps for a different type.
167
+
168
+
## Edit or delete work item types
169
+
170
+
To modify an existing work item type, click the **…** menu next to it and select **Edit**. You can update the name, description, icon, and background color.
171
+
172
+
To remove a work item type, click the **…** menu and select **Delete**. Existing work items of that type are not deleted — they retain the type until individually changed.
173
+
157
174
## Disable work item types
158
175
159
176
You can temporarily pause the creation of new work items for a specific work item type without affecting existing ones.
0 commit comments