Skip to content

Review 12.5 Release feature doc requirement needs

The following %12.5 Deliverable + direction + feature issues did not have a Documentation section in their description with documentation requirements for the feature work. Per the Product Development Flow and Documentation process, this is required when new or updated documentation is needed for the feature.

For most feature issues, docs will be required because there is a visible user or admin impact, or a capability that can't be leveraged unless it is documented. The requirements help the doc author (typically the feature engineer) make the complete set of updates to ensure the feature's discoverability and usability across use cases, and that reviewers are able to verify this was done.

  • Please add a checkbox when you have reviewed each issue below and, if it requires documentation, you've added the documentation label and some information on Documentation requirements in the description. If no docs are required, just check the box.
  • Please review and comment on this issue for any ideas or questions on documentation process for feature issues: technical-writing#69

Issues:

Edited by Marcia Ramos