> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/task-management/editing-your-tasks.md).
# Editing Your Tasks
As you become more comfortable using Tasks, you may find that certain fields need to be altered to better suit your business needs. This can easily be accomplished on your Mac by accessing **Settings > Edit Cards > Tasks** and then customizing your Fields.
Here is a list of the other fields that you can use for your Tasks. Check any of the boxes to make it a default field that is available for all Tasks.
### Category
This is available as a default because it is the simplest way to categorize your Task types. The Category field only lets you select one choice from the list.
### End Date
This field is automatically populated for you when you check a Task as done, however you are able to edit the end date.
### Estimated Time
This field estimates time each Task will take to complete. This can help you make decisions when choosing which Tasks to tackle during your working day. Some people find it helpful to add a period of time that should be allocated to achieving the Task. This is known as **Estimated Time**, and is helpful when choosing which Tasks to work on. You might only have 20 minutes so you would choose Tasks that are estimated to take 5-10 minutes to complete. When you have more time available you could tackle Tasks that are estimated to take longer, such as an hour or more.
## Files
Files can be added to most objects in Daylite and Tasks are no exception. This is helpful if you want to link a document that is relevant to the Task or you might add a URL link to a specific web page.
### Location
This is an optional text field that can be used to signify the location where the Task might be carried out. This field can also be used in Appointments. You can create a list of pre-defined Locations that will be selected from a list or you can add a custom location.
### Priority
Set your priorities on a scale of 0 None, 1 High, 2 Medium, or 3 Low.
### Start Date
This field is the date that the Task was started. By default this field is not populated automatically but you can customize Daylite to add it when you create a New Task.
To set the start date automatically navigate to **Settings > Default Values > Tasks > Automatically set start date = Yes**. This will add a Create Date that can be edited later if required.
### Status
This menu cannot be edited by the user. When a Task is created it is given the status of "Open", and when a Task is checked off it is given a status of "Done". The user can also change the status to "Cancelled" or "In Progress" if required.
### Type
This is also a menu that cannot be modified by the user. The default is "To Do" and there is no option to change the default from the Default Values section of Settings. The user can change the type of Task if required but it may be quicker to use Categories to define the type of Task instead. This field is normally suppressed when you first use Daylite.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.daylite.app/help/mac-fundamentals/task-management/editing-your-tasks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.