Adds asynchronous issue/epic update language for consideration.

Why is this change being made?

Currently Engineering Productivity uses a standup bot to communicate status, blockers, and other things. This is shared in the team slack channel. This proposal is to start using asynchronous issue updates (and epic updates) rather than a standup model.

The goals for this change are as follows:

• Align the reporting of status with people's context
• Single source of truth for status on any given issue
• An efficient and transparent way to communicate where an issue is at
• Asynchronous models of communication that scale with our team's timezone diversity
• Not intended to replace slack for support requests and socialisation

There's more in the MR itself but hopefully this summary will help folks assess the proposal's potential for achieving what is intended.

I've added the engineering productivity team as reviewers for this MR so please feel free to approve and remove as usual. I'd love some feedback if there are concerns on this idea.

Action

Please review the proposal and give feedback in the comment threads below!

/cc @gl-quality/eng-prod

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---