Skip to content

During Manage refinement, ensure issue description is updated

Drew Blessing requested to merge dblessing-refinement-description into master

Why is this change being made?

I've noticed when picking up issues recently that the description is often not updated to reflect the refinement process outcomes. It's necessary to parse through the discussion to understand the pieces that were decided upon, and often even to ask another question - for example: Based on the discussion, I believe the requested path is 1, 2 and 3?

It is helpful to the engineer that picks up the issue if the description is fully updated and indicates the work to be completed.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Merge request reports