How to write a useful feature request

Zeynep Demir 07.09.2026 09:10 1 replies 52 views
#1 07.09.2026 09:10

A useful request states the job to be done, who it is for, and what you already tried. A feature name without context is hard to schedule.

Screenshots, a short “why now”, and whether it is a Studio, front, or AACP problem help us put it on the public roadmap instead of bouncing it back for details.

Edited by — 07.09.2026 09:10
#2 07.09.2026 09:28

This is the bar we will use. Duplicate ideas will be linked rather than deleted. If two requests describe the same job, we keep the clearer thread and close the other with a pointer.

Forever CPalius **
Edited by — 07.09.2026 09:28