Commit 2289ce54 authored by Russell Dickenson's avatar Russell Dickenson

Merge branch 'msj-resource-events-api-notes' into 'master'

Add missing version notes to resource events API pages

Closes #225670

See merge request gitlab-org/gitlab!37449
parents a9c5768b d6af8f32
...@@ -1772,3 +1772,8 @@ Example response: ...@@ -1772,3 +1772,8 @@ Example response:
"akismet_submitted": false "akismet_submitted": false
} }
``` ```
## List issue state events
To track which state was set, who did it, and when it happened, check out
[Resource state events API](./resource_state_events.md#issues).
...@@ -2449,3 +2449,8 @@ Example response: ...@@ -2449,3 +2449,8 @@ Example response:
## Approvals **(STARTER)** ## Approvals **(STARTER)**
For approvals, please see [Merge Request Approvals](merge_request_approvals.md) For approvals, please see [Merge Request Approvals](merge_request_approvals.md)
## List merge request state events
To track which state was set, who did it, and when it happened, check out
[Resource state events API](./resource_state_events.md#merge-requests).
...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Resource milestone events API # Resource milestone events API
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31720) in GitLab 13.1.
Resource milestone events keep track of what happens to GitLab [issues](../user/project/issues/) and Resource milestone events keep track of what happens to GitLab [issues](../user/project/issues/) and
[merge requests](../user/project/merge_requests/). [merge requests](../user/project/merge_requests/).
......
...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Resource state events API # Resource state events API
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35210/) in GitLab 13.2.
Resource state events keep track of what happens to GitLab [issues](../user/project/issues/) and Resource state events keep track of what happens to GitLab [issues](../user/project/issues/) and
[merge requests](../user/project/merge_requests/). [merge requests](../user/project/merge_requests/).
......
...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -6,6 +6,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Resource weight events API # Resource weight events API
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/32542) in GitLab 13.2.
Resource weight events keep track of what happens to GitLab [issues](../user/project/issues/). Resource weight events keep track of what happens to GitLab [issues](../user/project/issues/).
Use them to track which weight was set, who did it, and when it happened. Use them to track which weight was set, who did it, and when it happened.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment