Add Release Notes - BCROS Home Page (Footer)

[LizGovier]

FIGMA FILE (Finished)

• [ ] https://bcregistry.gov.bc.ca/
• [x] https://account.bcregistry.gov.bc.ca/request-name
• [ ] https://bcregistry.gov.bc.ca/ppr-marketing/
• [ ] https://developer.api.bcregistry.gov.bc.ca/ Name Request
• [ ] https://names.bcregistry.gov.bc.ca/ BC Registries Dashboard
• [ ] https://bcregistry.gov.bc.ca/dashboard/ My Business Registry Business Search
• [ ] https://search.business.bcregistry.gov.bc.ca/ Asset Registry
• [ ] https://assets.bcregistry.gov.bc.ca/dashboard? As a BC Registries user, I need to have access to the latest release notes when logged in and while logged out.

Notes:

• Would like to remove release notes all together from what's new because eventually a new set of pages will be created to support some of these release activities
• Start creating that new user behaviour so users become familiar with the new location

Placement Options

• Footer
• header
• Paragraph on the landing page (logged off)
• Is there a place in the dashboard when user logs in?

User Types: Qualified Suppliers BC Registries Staff

BC Registries Landing Page (https://www.bcregistry.gov.bc.ca/)

Logged in User

[LizGovier]

Hey @trishreimer

I've sent a couple of options to the design team and will review with them tomorrow at our design meeting. Could you take a quick glance over the ticket incase there is anything I missed.

[trishreimer]

Update: As a BC Registries user, I need to see latest release notes when logged in (What's new) OR not logged in.

[LizGovier]

@trishreimer

Question

• Is the 'What's New' section only for product release information, or is it news and updates?

  ---

Bug When I click on 'What's New' a modal to the right appears. When I scroll halfway down the modal, the modal stops and the main screen starts scrolling leaving the user unable to view all the content in the modal.

Private Zenhub Video

[trishreimer]

The news and updates are mainly used for product releases...basically, anything new we want to tell people. It's possible it could be used for news/updates, like new legislation, authy not supportive, etc.

FYI - I'd like this solution to be simple and low effort as we have a long term vision for this release info to build out some pages.

[LizGovier]

Hey @trishreimer,

I've review this with the team and ready for your review. Let me know if you have issues access the Figma file.

Figma Design

Suggest to keep ‘What’s New’ in the header while logged in the positional memory of our users already know where to find this feature so it wouldn’t make sense to move its current placement.

---

Suggested Updates Yellow header should stick to the top while scrolling so user always has access to the close button Side panel needs a scroll bar Make side panel full height of the page User browser stored cookies to track whether or not the user has seen the latest articles. Because some of the articles date back a year, only show top 5 or 6 (most recent with a link out view all button at the bottom).

---

Current Bug What’s New panel is broken when scrolling (see video above)

[trishreimer]

Alternatively, instead of making changes to the what's new module, could I please just add my release notes link to the footer?

[trishreimer]

Or could we please add the release notes link to another place on the landing page?

[trishreimer]

@LizGovier Then, maybe next step or longer term. We look at fixing the what's new module.

I'd like to remove release notes all together from what's new because eventually a new set of pages will be created to support some of these release activities

I'd like to start creating that new user behavior so they get familiar with the new location

Without getting user data, I think it is difficult to confirm that there is a positional memory of our users with what's new.

For background, the what's new location was always a temporary location.

[LizGovier]

@trishreimer When you have a moment, could you write down the long term goals for Release Notes so I can add them to the desciption. Thanks!

[trishreimer]

Long term vision includes;

• strategic roadmaps to demonstrate transparency and clear direction on where we're going
• provide capabilities capture trending client needs, with the ability to prioritize what to build next and align everyone on the roadmap. This will also help with ongoing online engagement and to help empower teams.
• release notes to demonstrate transparency and continuous improvement. (mvp built) -Potentially pages related to SBC Connect - for ministry partners. What it is, why they need it, value it will provide, how to get connected. etc.

[saragunnarsson]

Hi @trishreimer , Liz passed this on to me and I took a look at what we can do. In order to keep it low effort, adding footer links to both logged in and logged out state seems like the best approach. Any solution we have looked into that is worth spending time on, quickly turns into quite high effort. Are you ok with putting the release notes link in the footer?

[saragunnarsson]

Got confirmation footer links are good, we can move forward with that. Adding FIGMA FILE to description.

[severinbeauvais]

@OlgaPotiagalova Omid wants to know if our team wants to take this work on, or if it's something Names Team should work on.

In the past, our team has done some work in this repo (bcregistry) but we don't own it. It's been mostly other teams/devs working in this repo lately. commit history

cc: @ozamani9gh

[ozamani9gh]

Names Team will complete this work.

[ozamani9gh]

@fodiley Design team is asking for this to take priority.. can we groom this ticket and bring it in to Sprint Backlog. i removed another ticket from sprint backlog

[fodiley]

@ozamani9gh sure lets do this today

[fodiley]

Link for release note https://www.release-notes.bcregistry.gov.bc.ca/

[ozamani9gh]

code lives here: all you should have to do is add one more footer line and test it.

https://github.com/bcgov/sbc-common-components/blob/master/vue/sbc-common-components/src/components/SbcFooter.vue

[stevenc987]

Note: codes change is in auth-web/package.json and sbc-common-components

[ozamani9gh]

@stevenc987 can you get someone in Relationships team to release their code to prod so it picks up the new version of sbc-common-components. They can add release report to the release of this ticket so we know when its going to be released to prod . @seeker25 ?

[seeker25]

Yup let me take a look at the different versions then I'll deploy.

[seeker25]

deploying now

[ozamani9gh]

Thank you @seeker25 looks good in PROD.

@saragunnarsson please close ticket if you are happy with implementation to prod.

[seeker25]

There are probably a few more spots to be updated? The landing page repo / business repos etc. Your call

https://github.com/bcgov/bcregistry/blob/53217e62716b43317b0fb2e272c2f6aa32da7adb/package.json#L22

https://www.bcregistry.gov.bc.ca/

[ozamani9gh]

Names Team has finished the work. waiting on Assets

[ozamani9gh]

@arlentees do you have an ETA of when the footer for Assets applications will be updated to new version of SBC-common-components.

Please let me know and i can close ticket.

[arlentees]

@ozamani9gh we didn't get to this in our standup today - adding it to be discussed tomorrow

[ozamani9gh]

[Yesterday 4:55 PM] Gunnarsson, Sara CITZ:EX Hey Omid, I got a list of links from Ethan on the design team. There might be more spots as well, but it seems like a good start to see if the link shows up in these places:

Marketing Pages https://dev.bcregistry.gov.bc.ca/ https://dev.account.bcregistry.gov.bc.ca/request-name https://dev.bcregistry.gov.bc.ca/ppr-marketing/ https://developer.api.bcregistry.gov.bc.ca/ Name Request https://dev.names.bcregistry.gov.bc.ca/ BC Registries Dashboard https://dev.bcregistry.gov.bc.ca/dashboard/ My Business Registry Business Search https://dev.search.business.bcregistry.gov.bc.ca/ Asset Registry https://dev.assets.bcregistry.gov.bc.ca/dashboard?

Staff Access Staff Dashboard Staff Asset Registries Staff Business Registry FAS Staff Dashboard BC Registries and Online Services