> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/managing-projects-and-time.md).

# Managing Projects & Time

Outcome-based guides for running projects in We360.ai — billable time, sprints, and Jira sync.

These guides walk through the goals teams most often bring to the Projects & Tasks module: turning logged hours into project cost, running work in time-boxed sprints, and keeping a project aligned with Jira.

Each guide is task-first. For what every field, status, and view *is*, see the [Projects & Tasks reference](https://docs.we360.ai/reference/work-and-time-management/product/work-and-time-management/projects-and-tasks). To see where each control lives on screen, see the [Project Suite screens](https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/project-suite/projects).

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Track billable time on a project</strong></td><td>Set up billing so approved time turns into project cost.</td><td><a href="/how-to-and-best-practices/managing-projects-and-time/track-billable-time-on-a-project.md">Track billable time on a project</a></td></tr><tr><td><strong>Plan and run a sprint</strong></td><td>Organize work into a time-boxed cycle and carry over what isn't finished.</td><td><a href="/how-to-and-best-practices/managing-projects-and-time/plan-and-run-a-sprint.md">Plan and run a sprint</a></td></tr><tr><td><strong>Sync a project with Jira</strong></td><td>Keep tasks, worklogs, and fields aligned between We360.ai and Jira.</td><td><a href="/how-to-and-best-practices/managing-projects-and-time/sync-a-project-with-jira.md">Sync a project with Jira</a></td></tr></tbody></table>


---

# 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.we360.ai/how-to-and-best-practices/managing-projects-and-time.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.