# Mapping status field

Syncing your **Status** field between Notion and Productlogz allows for seamless tracking and management of your feature requests, feedback, and product updates. By mapping the **Status** field correctly, you ensure that changes in one platform are reflected in the other, keeping your team aligned and reducing manual updates.

### Why This is Useful

* **Consistency Across Tools**: Keep your workflow synchronized without manually updating statuses in Notion and Productlogz.
* **Real-time Updates**: Ensure that any status changes made in Notion are automatically reflected in Productlogz, and vice versa.
* **Improved Workflow Management**: Helps product teams manage feedback and feature development efficiently.
* **Automated Tracking**: Reduces errors and ensures stakeholders always have up-to-date information.

### How to Map the Status Field

#### Step 1: Identify Status Fields in Notion and Productlogz

* In Notion, locate the **Status** property in your database (e.g., "To Do," "In Progress," "Completed").
* In Productlogz, identify the corresponding status categories (e.g., "Planned," "In Development," "Shipped").

#### Step 2: Set Up Field Mapping

1. Go to **Integrations** in Productlogz.
2. Select **Notion Sync** and connect your Notion workspace.
3. Choose the Notion database where your feedback or tasks are stored.
4. Select the **Status** field from Notion and map it to the equivalent **Status** in Productlogz.
5. Save the mapping.


---

# Agent Instructions: 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:

```
GET https://help.productlogz.com/integrations/productlogz-and-notion/mapping-status-field.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.