Is there an existing issue for this?

• I have searched the existing issues

Summary

Could you confirm when Custom Intake Forms will be available in Enterprise self-hosted, especially the commercial AIO image?

Plane Cloud already appears to have Custom Intake Forms. This is enough for our immediate use case; we do not need Intake forms to apply Work Item Templates for this request.

Why should this be worked on?

We use Enterprise self-hosted/AIO. Custom Intake Forms would let us collect structured bug reports, feature requests, and internal requests from non-project members, then hand those structured fields to our workflow automation and AI/bot-assisted triage.

A target version or release channel would help us decide whether to wait for the official AIO image, use a split/Prime deployment temporarily, or keep a sidecar form/webhook integration.

What I found:

• The Plane Cloud changelog entry "New navigation, custom Intake forms, threaded replies" says users can create shareable forms from custom Work Item types, choose which fields are shown/required, and create Work Items in Project Intake with the right fields and type already set.
• The public Intake Forms docs describe custom forms built from project work item types and selected properties.
• The self-hosted changelog currently only shows the v2.5.4 custom Intake form bugfix; I could not find a self-hosted release note saying the full Custom Intake Forms feature is available in AIO.
• The v2.6.0-rc4 commercial split backend image appears to include the custom Intake Form model/API path using work item type + selected form fields.
• The commercial AIO image tag plane-aio-commercial:v2.6.0-rc4 was not available in the registry when I checked; stable is available.

Questions:

• Is Custom Intake Forms planned for Enterprise self-hosted/AIO?
• If yes, which release should we expect it in, for example v2.6.x stable or a later AIO tag?
• Is this feature gated by Business/Enterprise plan, license, or a feature flag in self-hosted deployments?
• If the split commercial deployment receives this before AIO, is AIO expected to catch up in the same release cycle?