Completed bug and performance issues for the RP

This triage issue helps ensure bug fixes and performance improvements are included in the monthly release post.

To be included, the issues must:

1. Be closed.
2. Include both the correct milestone and the workflowcomplete label.

For each issues below, you should:

1. Determine if the issue has been completed.
2. If yes:
   • Add the workflowcomplete label.
   • Confirm the milestone is correct.
   • Make sure the issue is closed.
3. Check off the task item to show it's been reviewed.

pipeline_execution Frontend issues

Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @drew:

• Delayed job tooltip shows format string for rem... (gitlab-org/gitlab#538081 - closed) - workflowin review

pipeline_execution Backend issues

Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @drew:

• Multiple requests to the post-the-build-status-... (gitlab-org/gitlab#365615) - workflowin review
• No Notifications for Failed Scheduled Pipelines (gitlab-org/gitlab#36806 - closed) - workflowverification

pipeline_authoring Backend issues

Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @manuelgrabowski:

• "command should be an array of strings" when us... (gitlab-org/gitlab#517479) - workflowin review
• Backend: rules:changes impacted by diffs limits (gitlab-org/gitlab#433257) - workflowin review

Missing workflowcomplete and missing issues

Closer to the end of the milestone, you should:

• Check the issue list for completed issues that don't have the workflowcomplete label.
• Review Merge Requests for any fixes without a corresponding issue, and create issues for them.