Add 'Scheduled' status to engagement models#14319
Open
Conversation
github-actions
bot
added
the
New Migration
valentijnscholten
approved these changes
Feb 13, 2026
Maffooch
force-pushed
the
add-scheduled-engagement-status
branch
from
ff0efe1 to
2d7feba
Compare
Contributor
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
bot
added
conflicts-detected
docker
settings_changes
Contributor
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
github-actions
bot
removed
docker
settings_changes
github-actions
bot
removed
unittests
integration_tests
ui
parser
helm
localization
lint
labels
blakeaowens
approved these changes
Feb 16, 2026
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
3 participants
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.
Introduce a new 'Scheduled' status to the engagement and engagementevent models, enhancing the status options available for these entities. This change includes necessary database migrations to accommodate the updated status choices.
[sc-12790]