# Roadmap

{% hint style="info" %}
One day, this roadmap will be replaced by a [Product Roadmap](/boards/product-roadmap.md) of our own, but that's - uh, still on our roadmap. 😅
{% endhint %}

{% hint style="warning" %}
**This roadmap is subject to change**

Please be careful with decisions based on this information.
{% endhint %}

## Currently working on

These functionalities are currently in the making.

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f513">🔓</span> <del>Magic link login</del> ✅</summary>

In most cases, you'll trust your stakeholders, but when you need to be sure or when you have a sensitive project, you'll want to protect your board. We're working on a login functionality so you can secure your board and be sure the commenters are who they say they are.

</details>

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f514">🔔</span> <del>Email Notifications</del> ✅</summary>

When your customer has no idea you asked something, the communication can become quite one-sided. After being logged in, clients will be able to subscribe to issues. If anyone comments on it, we'll send them a notification by mail.

</details>

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f513">🔓</span> <del>Security settings</del> ✅</summary>

You can now limit the access to your boards by adding allowed domains in [security settings.](/boards/kanban-board/security-settings.md)

</details>

<details>

<summary>🗃️ Kanban board improvements</summary>

We're currently working on finetuning our Kanban experience: hiding old issues, showing more details like labels and links, tweaking the layout of issue descriptions, implementing a better editor, etc.

Next to these tweaks, we're also working to resolve all [known limitations](/boards/kanban-board/known-limitations.md).

</details>

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f514">🔔</span> Project updates</summary>

* Fetch project updates from Linear and show them in the Kanban view
* Send updates via email to stakeholders who subscribe to project updates.

</details>

## Short term considerations

Functionality that's being considered for the short-term future.

<details>

<summary>🎛️ Boards based on custom Linear views</summary>

</details>

<details>

<summary>🛟 Support ticket system</summary>

</details>

<details>

<summary><mark style="color:red;">♦️</mark> Product roadmap</summary>

</details>

<details>

<summary>🏷️ Changelog</summary>

</details>

## Long term considerations

These functionalities will probably need some more time but are considered for the medium/long term.

<details>

<summary>📝 Custom forms &#x26; request types</summary>

For now, all new requests are completely composed by your stakeholders. Sometimes that goes wonderful, but often you'll go back and forth to gather additional information regarding their bug or feature request.

With custom forms, you'll be able to create different types of requests (feature requests, bug reports, etc.). For each request, you'll be able to ask specific questions and make those fields required.

</details>


---

# 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://docs.publicboards.com/product/roadmap.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.