Skip to content

Additional contact loses the contextual label when a contact is added #19615

Open
@randimays

Description

@randimays

Description

On Resources & Support content types, such as Checklist, there is a box to add Contact information. In the contact information box, you can add an Additional contact. But once you choose Email address or Phone number, the label for Additional contact disappears. This likely doesn't affect the editor experience, but would be helpful from an engineering perspective to keep that label.

Before

After

User story

AS AN engineer or editor adding a Resources & Support content type such as Checklist and am adding Contact information, specifically an Additional contact
I WANT the label 'Additional contact' to always display, and not disappear when I choose Email address or Phone number
SO THAT at a glance I know that I'm adding information to the Additional contact section

Engineering notes / background

Analytics considerations

Testing & QA

Scope / Impact analysis

What, if anything, could break as a result of this change?
Engineer should assess this when approaching PR.

Roles / assignments

After functional testing, code review, accessibility review, and design review can happen in parallel.

  • Functional testing:
  • Code review:
  • Design review:
  • Accessibility review: Laura Flannery
  • Product acceptance:

Acceptance criteria

ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.

  • When an editor et al creates Resources & Support content (such as Checklist), , and in the Contact information section, and clicks Email address, the section title remains visible 'Contact information'.
  • When an editor et al creates Resources & Support content (such as Checklist), , and in the Contact information section, and clicks Phone number, the section title remains visible 'Contact information'.
  • Impact analysis is filled out and QA test plan is updated accordingly
  • Does this product have an existing regression test plan?
    • Yes, link:
    • No, regression test plan will be created as part of the work / points in this ticket

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions