Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facility address should not be displayed on FE when editor selects "Use the facility's street address" #17514

Closed
6 tasks
mmiddaugh opened this issue Mar 13, 2024 · 10 comments
Assignees
Labels
CY24-Q2 Calendar year Q2 2024 priority Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team

Comments

@mmiddaugh
Copy link
Contributor

mmiddaugh commented Mar 13, 2024

Description

In Tugboat, the VAMC Top Task pages and VBA Service accordions are displaying the Facility Address when "Use Facility Address" is checked in the Service Location. This is not the desired behavior. VAMC service accordions currently have the correct behavior.

Examples from Tugboat

VAMC Top Task Page - Los Angeles

Screenshot 2024-03-28 at 12 56 23 PM

VBA Facility Service Accordion - Cleveland

Screenshot 2024-03-28 at 12 57 08 PM

VAMC Facility Service Accordion - Pittsburgh

Screenshot 2024-03-28 at 1 17 29 PM

Eng notes

In the liquid template, for the address under the "name of clinic heading": a conditional is missing to check if the "use facility street address" checkbox is checked, before printing.

Acceptance Criteria

  • If "use facility street address" box is checked, do not show the street address on the front end
  • If "use facility street address" box is not checked, the user will be prompted to enter a street address, which should be displayed on the front end
  • Applies to these templates
    • VAMC Top Task pages (Billing and Insurance, Register for Care, Medical Records)
    • VBA Facilities -> Service accordions
    • VAMC Facilities -> Service accordions [Currently working as intended, but including to check for regression]
@mmiddaugh mmiddaugh added Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team labels Mar 13, 2024
@xiongjaneg xiongjaneg added the Regional office CMS managed VBA product owned by the Facilities team label Mar 19, 2024
@davidmpickett
Copy link
Contributor

By contrast, the VBA facility services on Tugboat currently are showing the Facility Address when this box is checked. See Cleveland VA Regional Benefit Office -home loans.

Screenshot 2024-03-20 at 6 03 53 PM

This is not what the Figma design shows, so would want to make sure @thejordanwood signs off on the proposed direction for both these cases.

@xiongjaneg
Copy link
Contributor

Take to UX sync to discuss current behavior in VAMC (not showing address), but VBA is different.

@davidmpickett
Copy link
Contributor

For reference, here is a previous ticket where the current logic was implemented #7339

@thejordanwood
Copy link

@davidmpickett I agree with the logic on the ticket you linked.

Correct logic for the "use facility street address" checkbox according to the following:

if "use facility street address" box is checked, do not show the street address on the front end - show only wing/floor/room info
if "use facility street address" box is not checked, the user will be prompted to enter a street address, which should be displayed on the front end

Additional logic would include:

If "use facility street address" box is checked and no wing/floor/room info is added, then nothing should show for this section.

@davidmpickett davidmpickett changed the title Service location: Should facility address be displayed when editor selects "Use the facility's street address"? Service location: Facility address should not be displayed on FE when editor selects "Use the facility's street address" Mar 27, 2024
@davidmpickett davidmpickett changed the title Service location: Facility address should not be displayed on FE when editor selects "Use the facility's street address" Facility address should not be displayed on FE when editor selects "Use the facility's street address" Mar 27, 2024
@davidmpickett
Copy link
Contributor

Thanks @thejordanwood! I am going to update this ticket to turn it in to a ticket to implement the desired behavior

@davidmpickett davidmpickett added Needs refining Issue status and removed Drupal engineering CMS team practice area labels Mar 28, 2024
@eselkin
Copy link
Contributor

eselkin commented Mar 28, 2024

We have to modify the liquid template a bit. Not a big lift, but worthy of at least 2 points. The conditional needs a bit of restructuring and testing.

@jilladams jilladams removed the Needs refining Issue status label Apr 10, 2024
@davidmpickett davidmpickett added the CY24-Q2 Calendar year Q2 2024 priority label Apr 11, 2024
@mmiddaugh
Copy link
Contributor Author

@jilladams @davidmpickett
@aklausmeier and I discussed this work and agree that although it needs to be addressed, it is not a launch blocker.

@davidmpickett
Copy link
Contributor

@jilladams @davidmpickett @aklausmeier and I discussed this work and agree that although it needs to be addressed, it is not a launch blocker.

Thanks. I updated it's position in the launch plan and the sprint 2 draft plan to reflect this.

@eselkin
Copy link
Contributor

eselkin commented May 13, 2024

Started to do this but then realized I can't test since data is not available from any mirror of prod yet and the SL tugboat ceased to exist after the merge.

@davidmpickett
Copy link
Contributor

Confirmed on prod for VAMC top task pages
Screenshot 2024-05-16 at 12 57 37 PM

Can't confirm VBA on Prod, but seems like this was done in a partial template and should fix all service locations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CY24-Q2 Calendar year Q2 2024 priority Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

6 participants