Paragraph [Add more] button label not respecting field widget settings

[davidmpickett]

Describe the defect

AS A UX writer working on the Drupal CMS editorial interface
I NEED to specify the text that appears on buttons
SO THAT I can make the interface intuitive for CMS editors

However, for the case of Paragraph widgets, the label/title of [Add more] button is not respecting the text I enter into the Widget settings. I first noticed this on the Spotlight content paragraph type on Vet Centers. But I have also tested it on Service Location paragraph for VAMC Facility Service and VBA Facility Service. Not working.

I have a theory that there is a collision happening between the Paragraphs module (stable) Field Widget (code) and the Change Labels module (code) but don't have the Drupal chops to test if that's true, or if there's an entirely other part of our codebase that's ignoring overriding both of these things

This might be related to this upstream issue in the Paragraphs Module

To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

AC / Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Additional context

Add any other context about the problem here. Reach out to the Product Managers to determine if it should be escalated as critical (prevents users from accomplishing their work with no known workaround and needs to be addressed within 2 business days).

Desktop (please complete the following information if relevant, or delete)

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Labels

(You can delete this section once it's complete)

• Issue type (red) (defaults to "Defect")
• CMS subsystem (green)
• CMS practice area (blue)
• CMS workstream (orange) (not needed for bug tickets)
• CMS-supported product (black)

Team

Please check the team(s) that will do this work.

• CMS Team
• Public Websites
• Facilities
• User support
• Accelerated Publishing

[xiongjaneg]

@maortiz-27-80 Dave found this defect and it appears to affect more than Facilities products. Dave also noted a potential related upstream Drupal issue and noted it in the ticket description. Noting it is preventing us from implementing some UX recommendations on CMS interfaces.

Thanks for your consideration!

[maortiz-27-80]

Thanks for flagging, @xiongjaneg ! The team will review/refine and let you know if we have any questions. cc: @BerniXiongA6

[BerniXiongA6]

Hey @edmund-dunn would you be able to pre-refine this ticket ahead of or by Sprint Planning 101? Let @maortiz-27-80 and/or me know if you wanted to sync up or if you could do this async.