Include a brief description of the problem being solved and why this
approach was chosen. Mention risks or shortcomings with this solution.
Provide relevant background information such as the associated issue, links
to design documents, screenshots, and performance measurements.
Even small changes deserve a little attention to detail. Put your change in
context.
Worked when I tested links locally, but once it was live, the URL is now incorrect resulting in a 404 error
Connected to #
Testing Notes / Validation Steps
Explain how this change has been tested and what cases/conditions are
covered. Enumerate the steps someone might take to manually exercise this
change. Detail is important!
You can recommend one-time manual testing when someone validates your
changes. Rely on automation when trying to verify that a change remains in
place. Automated tests should be included in this PR.
Description
Worked when I tested links locally, but once it was live, the URL is now incorrect resulting in a 404 error
Connected to #
Testing Notes / Validation Steps