Add a case reference to data breach form #1799
Merged
Conversation
This file contains 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
Add a unique case reference to the data breach form to prevent incorrect threading by GMail. Requires mysociety/alaveteli#7967 Fixes #1774
gbp
force-pushed
the
1774-db-form-case-ref
branch
from
a2bd270
to
f1c0425
Compare
gbp
approved these changes
Oct 26, 2023
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.
Add a unique case reference to the data breach form to prevent incorrect threading by GMail.
Requires mysociety/alaveteli#7967
Fixes #1774
Screenshots
Note that I changed the prefix from "BREACH" to "BR" after the screenshot as "BR" maps more closely to our tracker sheet refs.