Publish status page on issue changes
What does this MR do?
Part of #205168 (closed). Contributes to #205165 (closed).
This MR hooks into the create, update, reopen, and close services of issues to trigger a status page update.
Future MRs will hook into note creation/update/deletion and award creation/deletion.
| Action | Publish to Status Page |
|---|---|
| Create public issue | |
| Create confidential issue | |
| Update public issue related fields | |
| Update public issue unrelated fields | |
| Update confidential issue fields | |
| Make issue public | |
| Make issue confidential |
|
| Close public issue | |
| Close confidential issue | |
| Close external issue | |
| Reopen public issue | |
| Reopen confidential issue |
This MR is behind a beta feature flag and we tracking the rollout in #210026 (closed) hence also the missing changelog entry.
Screencasts
| Adding new public issue and closing/reopening | Adding new confidential issue and make it public again |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
- [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
- [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Peter Leitzen