> For the complete documentation index, see [llms.txt](https://docs.released.so/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.released.so/guide/product/roadmaps-and-ideas/views.md).
# Views
## Board view
For most roadmap communication, the Board view is ideal — it shifts the focus from specific dates to broader goals, priorities, or any structure you define.
Because Roadmaps in Released are highly flexible — allowing you to include work items from multiple projects — each view type requires a bit of setup. You’ll find setup instructions for each view below.
#### Configuration
Map work items to columns on the roadmap based on their status or field options. This can include criteria such as teams, quarters, priority, and more.
To customize the column mapping:
{% stepper %}
{% step %}
Select **Display options**
{% endstep %}
{% step %}
Click **Edit columns**
{% endstep %}
{% step %}
Select the field you want to map for each project
{% endstep %}
{% step %}
Map your field options by dragging them to the corresponding column
{% endstep %}
{% endstepper %}
#### Supported field types
The following field types are currently supported for column mapping.
• Status
• Select (Multi-select is not yet supported)
• Version
Support for additional field types, including date-based columns, is planned for future updates. Please [let us know](https://released.so/support) if you would like us to support a specific field type.
## Timeline view
Timeline roadmaps provide a visual, Gantt-style bar chart of your project schedule — showing when work starts and ends, how phases connect, and where dependencies exist.
This format helps teams and stakeholders quickly grasp the full project plan, track progress, and manage sequencing.
Since confidence in delivery dates decreases the further out you plan, using fuzzy dates (months or quarters) help communicate uncertainty clearly. This gives stakeholders a more accurate picture of what’s planned — and how fixed or flexible those plans are.
#### Configuration
For each project, you can define which start and end date fields should be used to position items on the timeline. Released will make an initial best guess based on your project data, but you can update these fields at any time.
Date field configuration for the timeline view
This gives you the flexibility to use different date fields across different projects — ideal if teams track timelines in different ways.
---
# 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.released.so/guide/product/roadmaps-and-ideas/views.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.