-
Notifications
You must be signed in to change notification settings - Fork 0
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
Dead links in security statement and audit links in policy docs #1735
Comments
Please add your planning poker estimate with Zenhub @mtoutloff |
Please add your planning poker estimate with Zenhub @YedidaZalik |
Gabe flagged in a support ticket that this broken link also appears in the TOU: when clicking low-sensitivity personal information in Will scan the other policy docs to see if the broken link appears anywhere else. |
We have a test to check for dead links, but it wasn't alerting us due to bug. The card for this is here: |
Current broken links:
|
Fixed the email formatting link from GCA |
Ok now that the test are passing, here is the latest list of failures: |
@yaelberger-commits @mtoutloff could we expand the scope of this card to address all of the above? |
@andrewleith is this card done now? I thought we replaced or removed any that were broken? |
Describe the bug
Our links out to the Standard on Security Categorization from the Security Statement are broken so we need to replace them with updated links in EN and FR
Scan all our policy docs for links to assess if we should link out to other pages or not, if it's necessary
Bug Severity
See examples in the documentation
SEV-3
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When you click the link to Protected A, or the paragraph about Protected A, you should get taken to this page for the Directive on Security Management https://www.tbs-sct.canada.ca/pol/doc-eng.aspx?id=32614
Impact
Broken links create frustration and impede users from completing their tasks to learn about Notify and onboard.
If applicable
Impact on Notify users: Broken links cause furstration
Impact on Recipients: None
Impact on Notify team: None
Screenshots
Additional context
As per @YedidaZalik suggestion, in this case we will add another line introducing the link: eg. "For more information on Protected A, degree of injury and federal security levels, read the Directive on Security Management" or something like that. Then if the link changes in future, they can at least search for the title.
@mtoutloff agrees, and suggested we only link to it once.
The text was updated successfully, but these errors were encountered: