Task Templates let you reuse a prepared task structure instead of building the same set of tasks every time. A template can create one task or a group of tasks with subtask templates, then attach the new tasks to a post, page, or supported custom post type.
How This Fits In OrbitalWP
Task Templates are managed separately from live tasks. When you apply a template, OrbitalWP creates new tasks from that template while keeping the template available for future use.
Templates can include nested subtask templates. When applied, OrbitalWP keeps that hierarchy so the created tasks and subtasks match the structure of the template.
Where To Find It
In the WordPress admin, open Orbital and choose Templates. The submenu label is Templates, and the page title is Task Templates.
You can also apply templates from supported content edit screens. In the Related Tasks area, users with the right access may see Use Template.
Template availability for content types is controlled in Orbital > Plugin Settings, on the General tab, in the Task Templates section under Allowed Post Types for Templates.
Before You Start
- By default, creating, viewing, and applying task templates are administrator-controlled actions.
- The template you want to apply must be a published top-level template.
- Child subtask templates are included through their parent template; they are not selected as separate starting templates.
- To apply a template to a post or page, you need permission to edit that content item.
- If post type restrictions are configured, the target content type must be allowed for templates.
What You Can Do
- Create reusable task templates.
- Add a Template Description to explain when the template should be used.
- Add Subtask Templates to build a repeatable checklist or workflow.
- Apply Template from the Templates list.
- Use Template from a supported content edit screen.
- Attach created tasks to a post, page, or supported custom post type, or leave them as standalone tasks.
- Add a task name prefix before the tasks are created.
- Preview the task names and hierarchy before applying the template.
Basic Workflow
- Open Orbital > Templates.
- Choose Add New Template and create the main template task.
- Add a clear title, task content, and optional Template Description.
- Publish the template when it is ready to be used.
- Use Add Subtask Template on the template edit screen, or Add A Subtask from the Templates list, if the template should create subtasks.
- Choose Apply Template from the Templates list, or Use Template from a supported content edit screen.
- In the Apply Template panel, choose a template, optionally attach it to a post, adjust the naming options, then choose Apply Template.
Important Controls And Settings
- Select Template chooses the published top-level template to apply.
- Attach to Post (Optional) lets you search for a content item. If you leave it empty, OrbitalWP creates standalone tasks.
- Include parent post title in task names adds the selected post title before each created task name.
- Task Name Prefix (Optional) adds your own prefix before each created task name.
- Preview shows how the created task name will look before you apply the template.
- Allowed Post Types for Templates controls which public content types can have templates applied from their edit screens.
What Affects What You See
Users may see different template controls based on their WordPress and OrbitalWP access. A user who can edit tasks may still be unable to manage templates or apply a template to a content item they cannot edit.
The template selector only includes templates the current user can read and apply. Templates may be hidden if they are unpublished, nested under another template, unavailable to the current user, or too large to apply.
The Use Template button on a content edit screen depends on task creation access, relationship access, available published templates, and the post type settings for templates.
Deeper Notes
When a template is applied, OrbitalWP copies the template title, content, hierarchy, task data, terms, and featured image into newly created tasks where those items are available.
Restricted workflow fields are permission-aware. Approval status, closed state, and assignee may be reset instead of copied if the applying user is not allowed to set those fields.
Created tasks may be published, draft, or pending depending on the applying user’s task permissions. If published tasks with assignees are created, notifications still depend on notification settings and recipient access, and a template that creates multiple tasks may produce a summary email instead of separate emails for every task.
A single template can include up to 100 tasks and subtasks. Larger template structures are not available for normal application.
Common Problems
I cannot see Templates. Template management is restricted. Ask an administrator to check your access.
I cannot see Use Template on a post or page. Check whether you can edit that content item, whether you can create and relate tasks, whether at least one published template exists, and whether that post type is allowed for templates.
The template is missing from Select Template. The template may not be published, may be a child template, may include items you cannot read, or may exceed the template size limit.
Apply Template is disabled. Select a template first. The button becomes available after a valid template is selected.
The new tasks were not attached to the post. Make sure a post was selected under Attach to Post (Optional). If that field is left empty, OrbitalWP creates standalone tasks.
The task names look different than expected. Check Include parent post title in task names and Task Name Prefix (Optional). Those controls change the names before the tasks are created.
Assignee, approval, or closed state did not copy from the template. Those fields are restricted. A user with the right approval or assignee- management access may need to update the created tasks afterward.
An email did not send. Template-created task emails depend on notification settings, assignee data, task status, recipient mute settings, and whether the recipient can read the created task.