> For the complete documentation index, see [llms.txt](https://docs.withluna.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.withluna.ai/roadmaps/custom-fields.md).

# Custom fields

## Create custom fields

Custom fields provide additional data about your launches and can enable prioritization frameworks.

1. Click the **eye icon** at the top of the roadmap table
2. Click "**Create new field**"
3. Configure the field:
   * **Field name** (e.g., "Engineering Effort", "Client Tier", "Revenue Impact")
   * **Field type:** Text, Number, Formula, Rating, Multi-select
   * **For formula fields**: Reference other native or custom fields for calculations
4. Click "Create"

The custom field appears as a new column in the roadmap table.

## Application: use custom fields for prioritization

**Example: RICE score framework** 

* Create a formula field that calculates prioritization scores: `(Reach * Impact * Confidence Level * 2) / RICE Effort`
* Where Reach, Impact, Confidence Level, and Effort are individual custom fields.

**Benefits:**

* Sort launches by calculated priority scores
* Make data-driven roadmap decisions
* Standardize prioritization across teams
* Track business impact metrics


---

# 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.withluna.ai/roadmaps/custom-fields.md?ask=<question>&goal=<endgoal>
```

`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.