Repository navigation
[SC-18574] Document configuring default fields per artifact type - #1526
Merged
even-steven merged 4 commits intoOct 6, 2026
Merged
Conversation
…type Default fields are now configured from Settings > Artifact Fields instead of the Fields checkboxes in the Artifact Type pop-up, and each field can be shown on creation and required on creation per type. - manage-artifact-fields: new "Configure default artifact fields" section (Enabled, Show on creation, Require on creation, the fixed rules for Risk Area, Status, Attachments and the remediation plan, and the workflow warning). The Default Fields paragraph links to it. - _add-edit-artifact-types: drop the Fields step and its footnotes; a new type starts with every default field on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 of 11 tasks
cachafla
approved these changes
Oct 1, 2026
Base automatically changed from
stevenchand/sc-18572/1-show-artifact-default-field
to
main
October 5, 2026 16:30
…3-configure-artifact-default-
…Risk Area off Kept SC-18573's Name, Description and Slug steps and slug footnote; the Fields step and its footnote stay removed, as this branch moves field configuration to Artifact Fields. The new-type note now says Risk Area starts off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
even-steven
deleted the
stevenchand/sc-18574/3-configure-artifact-default-
branch
October 6, 2026 16:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description
What and why?
Documents configuring default artifact fields per artifact type.
manage-artifact-fields.qmd: new "Configure default artifact fields" section covering Enabled, Show on creation and Require on creation, the per-field rules, and the workflow warning._add-edit-artifact-types.qmd: the Fields step is removed, since the checkboxes are gone from the Artifact Type pop-up. This file is included bymanage-artifact-types.qmdand one training deck.How to test
Render
site/guide/validation/manage-artifact-fields.qmdandmanage-artifact-types.qmd.What needs special review?
Wording, and that the removed Fields step leaves the numbered steps coherent.
Dependencies, breaking changes, and deployment notes
_add-edit-artifact-types.qmd.Release notes
Documents configuring default artifact fields per artifact type.
Checklist
Not rendered locally (Quarto isn't installed here).
Shortcut: sc-18574
🤖 Generated with Claude Code