Disable/remove option to add suggestion to batch when only one suggestion exists on the MR page

Problem to solve

Recently we shipped !22439 (merged) (from a great community contribution, btw).

There is one scenario where we could potentially improve the UI.

If there is only one suggestion made on the whole MR, it doesn't make sense to add it to a batch.

We should not be recommending that, to avoid confusion. (Or should, we? UX)

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)
• Sam (Security Analyst)
• Rachel (Release Manager)
• Alex (Security Operations Engineer)
• Simone (Software Engineer in Test)
• Allison (Application Ops)
• Priyanka (Platform Engineer)
• Dana (Data Analyst)

User experience goal

Proposal

1. Hide/disable the button to add to batch

or

2. Do nothing to keep it consistent.

This depends on UX validation.

Documentation

Updating the suggestions section of the docs.

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references