Cor 3895 docs for beta release #947
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive beta documentation for DevCycle's Feature Status and Lifecycle Management system. The documentation explains how features move through different statuses (Development, Live, Completed, Archived) and the behaviors associated with each status category.
Key Changes:
- Introduces documentation for status-based lifecycle management with four default statuses
- Details the Completed status workflow including cleanup checklists and semi-read-only restrictions
- Explains custom status capabilities and category inheritance rules
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This update introduces a new section on managing Feature Statuses at the Project level, detailing how to view, create, edit, and reorder statuses. It also outlines permissions for status changes and the rules governing status categories.
Deploying devcycle-docs with
|
| Latest commit: |
f3c242c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e018d4a4.devcycle-docs.pages.dev |
| Branch Preview URL: | https://cor-3895-docs-for-beta-relea.devcycle-docs.pages.dev |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| This category represents Features that are actively being built, tested, or prepared for release. | ||
|
|
||
| By default, new Features are created in the **Development** Status. |
There was a problem hiding this comment.
Should this be Category instead of Status?
| - New Categories cannot be created | ||
| - Each Category must contain at least one Status | ||
| - The last remaining Status in a Category cannot be deleted | ||
| - Status labels and ordering within a Category can be modified |
There was a problem hiding this comment.
also statuses must have unique keys
| - Statuses in the **Completed** and **Archived** Categories can only be applied by users with the **Publisher** permission | ||
| - Only **Publishers** can create, and modify Feature Statuses in the Project Settings | ||
|
|
||
| ## Custom Statuses |
There was a problem hiding this comment.
The addition of custom statuses seems confusing to me. I feel liek we can just combine it with statuses, saying they can create additional 'custom' statuses
created new beta version of the Status & Lifecycle page which includes custom statuses