Add kls contact email on 500 page#637
Open
Dashue wants to merge 1 commit into
Open
Conversation
0751afb to
7078d8f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description of Change
Aim of this work was to:
Make KLS forms show contact email when 500
SNow ticket:
RITM0234473
🧪 Testing Completed
🔧 Manually tested
Select the environments where manual testing was carried out.
localdevtestUATpreprodDEV:
TEST:
UAT:
PREPROD
💁🏽 Have you attached evidence of the tests in this PR?
🦾 Automated tests
Have you added automated tests?
🌍 Environment(s) Affected
Untick as appropriate
🛠️ Execution Details
(Choose based on potential service impact)
🔄 Backout / Rollback Plan
🔗 Dependencies / Config Changes
🏷️ Change Type Recommendation
✅ Pre-Conditions / Pre-Checks
None
🔍 Post-Deployment Checks
Unsure if we can manually trigger 500 for KLS forms at will
📚 Documentation
Have you updated the documentation?