> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/task-management-in-the-designer.md).

# Task Management in the Designer

## Introduction

With LogicNets version 8+, you can define a specific "task" that collects all associated changes to the logicnet model. You can then share that list of actions online or export them for distribution. The system can maintain the tasks locally in the data.db (by default) or it can retrieve them from an Atlassian Jira installation. For more information, see [System Settings - Designer](/release-9/platform-documentation/system-administration/system-settings/system-settings-designer-tab.md).

## Description

Create a new task by navigating to the *Tasks* tab in the bottom Designer panel. You can create a task immediately if you use the data.db as a source, or you can configure the Designer to use Jira and then create a task.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-358a7d70b6a78ecbf79c8052e7e9ca666ddb314d%2Ff49b8083-d37b-4a60-b5c7-52c6269964bc.jpg?alt=media)

* If no tasks exist, you can complete the *Title*, *Description*, *State*, and *Assignee* fields and click ***Save*** to create one.
  * *State* contains system categories and you cannot customize it now.
  * *Assignee* is limited to users listed in the User Management module.
* To record changes against any task, you select the task from the list and click ***Activate***. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7259bdb6663b618a5893e8a7fbf77e442e793bc7%2F2d029b80-e0d1-4765-881c-82300b726a12.jpg?alt=media)
* Once you click ***Activate*** and until you click ***Deactivate***, the system associates all changelog entries with the task ID.
* The system displays the ID and title of the task in the header. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-93635dfaba3c196718521da2cc612cf6670d07f9%2F4f496ad8-a172-48cf-be08-a8946f8892b0.jpg?alt=media)
* You can export and/or filter the changelog to show only those changes associated with a specific task. See [Changelog Information in the Designer](/release-9/getting-started/the-logicnets-designer/designer-changelog-information.md) for more information.

## Designer Configuration

You can find information about configuring Task Management connected to a Jira project in [System Settings Designer Tab](/release-9/platform-documentation/system-administration/system-settings/system-settings-designer-tab.md).


---

# 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://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/task-management-in-the-designer.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.