#1883 Backwards compatibility for QTs #1919
Merged
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.
What's included?
We have new features to help with processing applications.
This is great for new exercises but here we are considering the impact on existing exercises. Some exercises will have been completed and, perhaps, archived. Other exercises with be 'part-way through' and so will have completed some application processing tasks.
We would like to:
Tasks
Closes #1883
Who should test?
✅ Product owner
✅ Developers
How to test?
This is all about getting exercises in the correct state. The following two states are relevant:
Exercise has finished processing applications
These exercises may well be left alone however we should be able to:
Exercise is part-way through processing applications
Any future tasks will be carried out as normal. Here we have ensured that for any 'expired' tasks we should be able to:
Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING