Change request management Using GitLab as a document lifecycle tool gives us strong collaboration and change request functionality. GitLab (and GitHub) use issue and milestone features to log and work through change requests. We can apply tags to these issues and group issues by milestone. When changes are approved, we can reference these issues and change requests in our merge requests that will ultimately update documentation. This allows us to carry through any change requests directly with the content changes - making analyzing content updates easier. Document lifecycle tools also give us options to integrate service desks and external issue trackers e.g., . We should generally add information on how to log issues on a document in a document's *CONTRIBUTING.md* file. This will tell collaborators how they can log an issue or how they can update any issue themselves.
1 minute read | Concept

Change request management

Using GitLab as a document lifecycle tool gives us strong collaboration and change request functionality.

GitLab (and GitHub) use issue and milestone features to log and work through change requests. We can apply tags to these issues and group issues by milestone.

When changes are approved, we can reference these issues and change requests in our merge requests that will ultimately update documentation. This allows us to carry through any change requests directly with the content changes - making analyzing content updates easier.

Document lifecycle tools also give us options to integrate service desks and external issue trackers e.g., https://gitlab.com/help/user/project/service_desk.

We should generally add information on how to log issues on a document in a document’s CONTRIBUTING.md file. This will tell collaborators how they can log an issue or how they can update any issue themselves.

Example

See also

Home | Contact | Examples