> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/account-intelligence/tasks-and-projects.md).

# Tasks & Projects

Create tasks and projects in order to track work being done for customers

## Tasks

Tasks are individual pieces of customer work either to be done by you or the customer.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2Fygmvc9BPEJCFPAxChxsN%2FCleanShot%202025-08-10%20at%2012.49.31%402x.png?alt=media&amp;token=6d3742f4-914b-4131-9822-4fa3ed8e2eaf" alt=""><figcaption></figcaption></figure>

Tasks can be created:

* Manually
* Automatically from calls with [AI Tasks](/pylon-docs/account-intelligence/tasks-and-projects/ai-tasks.md)
* Automatically as part of [Project Templates](/pylon-docs/account-intelligence/tasks-and-projects/project-templates.md)
* Through the [Tasks & Projects API](/pylon-docs/developer/api/api-reference/tasks-and-projects.md)

## Statuses

Custom task statuses allow you to create additional task states beyond the default statuses to represent your team's unique task lifecycles.

Go to the [Task Statuses](https://app.usepylon.com/settings/task-statuses) page in settings to create custom task statuses. Once created, you can set tasks to your custom statuses anywhere you can normally set task status.

## Projects

Projects are a collection of tasks organized into a set of milestones and optionally based off of a [Project Templates](/pylon-docs/account-intelligence/tasks-and-projects/project-templates.md).

Projects can rollup onto the account level so project progress can be visible at a glance on a book of business level. Additionally filter Tasks by Project and Project owner to find what's relevant to you.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FeYb5wrYjnD1Cd0CZ6KuB%2FCleanShot%202025-08-10%20at%2012.48.17%402x.png?alt=media&amp;token=4fb31bd4-eb58-498c-8b15-3fb8df39420a" alt=""><figcaption></figcaption></figure>

## Correct completion dates

You can correct the completion date of a task or milestone that is already complete. The date must:

* Be at or before the current time.
* Be at or after its start date, or its creation date if it has no start date.
* For a milestone, be at or after the latest completion date of its top-level tasks. Subtasks don't set this lower bound.

Changing a task's completion date can move its milestone's completion date forward to keep the milestone at or after its latest completed task.

## Subtasks

Subtasks allow you to break down complex tasks into smaller, manageable pieces of work.

Subtasks inherit the same account, project, and milestone as their parent task. Completing subtasks does not affect milestone progress, only the parent task's completion counts toward milestone tracking.

## Linked tasks

Use **Linked tasks** in a task's sidebar to record dependencies. Choose **blocks** when this task is a prerequisite for another task, or **is blocked by** when another task is its prerequisite. Editing links requires permission to edit Tasks.

A task can't block itself. Pylon also rejects duplicate links, links in the opposite direction between the same two tasks, and links that would form a cycle.

## Comments

Task comments enable your team and end-users to have discussions directly on tasks, creating a shared communication channel. End-users can leave comments on tasks from within the customer portal, while your team can comment from within Pylon.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FeKYX7uAIItnBxlWeIVih%2FTask%20Commenting.png?alt=media&amp;token=6dd1b317-0255-4c85-9695-8409b6d283fa" alt=""><figcaption></figcaption></figure>

## Product Tickets

You can link Pylon tasks to any of the supported [product ticketing integrations](https://docs.usepylon.com/pylon-docs/integrations/ticketing). External tickets (Linear issues, Jira tickets, etc.) require the integration to be connected to your Pylon workspace, then you can create & manage links from the Tasks sidebar.

When viewing Tasks, you can filter by product issues and visualize them as table columns.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FjZlhsfv1MNYmUtNYVX0j%2Fimage.png?alt=media&amp;token=eb6758dc-470b-4694-9bc1-e74fc65b0246" alt=""><figcaption></figcaption></figure>

Use the "task product ticket status changed" trigger kickoff, configurable from the product integration page, to set up automations based on product ticket changes.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FfLK3dunCMM09ZvAvnx1L%2Fimage.png?alt=media&amp;token=ce66aff2-a3b9-4ab1-9fb8-1447fb30d19a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FzZ0kX9DW1E30V6n3pUXa%2Fimage.png?alt=media&amp;token=75abb909-2400-4412-854a-020a2e495c75" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/account-intelligence/tasks-and-projects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.