# The Requests Board

https://dev.wisecp.com/es/the-requests-board

The requests board is where users and developers raise what the platform is missing: how a request is opened, what the states say and who sees which requests.

## Overview

The board is a discussion surface rather than a wish list. Each request stands in one person's own words; readers support it, comment on it and the team gives it a state.

Requests are not translated. A request stays in the language it was written in, and that language is recorded with it; the team does not rewrite the text.

For a developer the board does two jobs: you report the extension points you find missing, and you read what customers are asking for before you plan your own product.

## Prerequisites

- **A signed-in account**: Anyone can read the board. Opening a request, voting and commenting need an account.
- **A complete profile**: An unfinished account can read the board but cannot put words on it under its own name.
- **Moderator approval**: A new request waits for approval. It appears on the board when the team moves it out of the queue.

## Structure

A request sits in one of eight states. Everyone sees all but the first.

| State | What it says |
| --- | --- |
| Pending | Newly submitted; visible to its author and the team only |
| Under review | Published on the board, the team is reading it |
| Considered | The idea landed; its scope is being discussed |
| Planned | On the roadmap |
| In progress | Being worked on |
| Completed | Met by a published release |
| Declined | Will not be built; the reason sits under the request |
| Already possible | The need is met by the product as it is today |

The board sorts by state by default, so work in progress and planned items come first. Newest, oldest and top-rated sorting are available too.

## Walkthrough

### Open a request

1. Search the board first; when the same need is already open, support it instead of opening a second one.
2. Select **New Request** and write the need concretely: what you are trying to do and what stops you today.
3. After submitting, the request waits for approval. Once the team publishes it, it appears on the board and starts collecting votes.

### Support and discuss

1. Vote on a request when you share the need; votes are read during prioritisation.
2. Add something concrete in a comment: the scenario that needs it and your current workaround.
3. Add a request to your favourites to keep following it.

### Follow the outcome

1. When the state changes the badge changes with it; the record keeps the same address.
2. Declined and already-possible requests carry their reason under the record.
3. A completed request closes together with the release that met it.

## Reference

- **Language visibility**: Reading the site in English shows the requests written in English. Reading it in any other language lists the whole board.
- **Vote**: One vote per account. You may take your support back; the tally comes from the list of voters.
- **Comment**: Comments pass through moderation and sort by newest, oldest or most helpful.
- **Favourite**: Adds the request to your own list. It changes neither its visibility nor its order.
- **Who owns a request**: The text belongs to its author and is never translated. The team sets the state and does not rewrite the words.

## Example

A well-written request says three things: what you are trying to do, what stops you today and what it would solve.

```bash
Need   : a hook that runs before a service is created
Today  : I work from the post-create hook and cannot stop the order
Impact : I want to halt an order when the provider quota is full
```

The distance between a general wish ("make it more flexible") and a concrete scenario decides how quickly a request is assessed.

## Pitfalls

> **Opening the same need twice**
> 
> Duplicate requests split the votes and both stay under the threshold. Search first, and support the existing one when it is there.

> **The board is not a support channel**
> 
> Open a support ticket for a problem on your own installation. A record here discusses the product's future, not one installation.

> **A new request is not visible at once**
> 
> What you submit waits for approval first. If you cannot find it on the board, the record is not lost; it is in the queue.

## Related Articles

- [The Developer Portal](https://dev.wisecp.com/en/the-developer-portal)
- [Joining the Developer Programme](https://dev.wisecp.com/en/joining-the-developer-programme)
- [Developing for WISECP](https://dev.wisecp.com/en/developing-for-wisecp)