> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/feature-templates/assign-tasks/edit-task-screen.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://help.adalo.com/ja/feature-templates/assign-tasks/edit-task-screen.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.