Skip to content

Edited multi-select issues docs for style compliance

Russell Dickenson requested to merge docs/34504-review-multi-select-issues-docs into master

What does this MR do?

Edited multi-select issues docs for style compliance

- Moved to the section about moving cards, because this was more
  appropriate, and the previous section was marked as only being
  for enterprise features, but moving multiple cards is a Core
  feature.
- Changed the instructions into a brief procedure, to improve
  clarity.
- Modified instructions to remove mention of "left click" as this
  is not available on MacOS. Also marked keyboard keys as such, to
  improve clarity.
- Removed multi-select because it didn't reflect the feature's
  purpose.

Closes #34504 (closed)

Related issues

#34504 (closed)

Author's checklist

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports