Skip to main content
Use the feature-request portal linked from the StageMic website to suggest improvements. The most useful requests describe a real workflow and the problem you want to solve.

​
Check existing requests

Look for an existing request before creating a new one. If someone has already described the same need, add your use case or support that request through the portal.

​
Explain the problem

Describe:
  • What you are trying to achieve.
  • How you currently do it.
  • What makes the current process difficult.
  • How often the situation occurs.
  • Who would benefit from an improvement.
A practical example from a rehearsal or performance helps explain why the feature matters.

​
Suggest an approach

You can suggest a button, setting or workflow, but include the underlying need too. For example, “I need crew to distinguish a returned pack from one still with an actor” gives useful context beyond a particular interface proposal. Mention any effects the change might have on backstage displays, printing, OSC or existing show files.

​
Keep requests focused

Use one request per distinct feature where practical. Related details can stay together, but separate unrelated ideas so that each can be discussed and tracked independently.

​
Examples and privacy

Screenshots, sketches and small fictional examples are welcome. Avoid publishing licence keys, Crew passwords or private production and cast information.

​
Requests and release plans

Submitting a request does not guarantee that it will be implemented or included in a particular release. Features are considered alongside practical theatre use, reliability, complexity and compatibility with existing workflows.

​
Bug or feature request?

Report something as a bug when an existing feature behaves incorrectly. Submit a feature request when you want StageMic to support a new task or a different way of working. If you are unsure, explain the situation clearly and it can be categorised during review.