feat(workflow_engine): Add support to handle Activity events in the WorkflowEventData
#93580
Conversation
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
github-actions
bot
added
the
Scope: Backend
❌ 13 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
saponifi3d
added a commit
that referenced
this pull request
Jun 18, 2025
…93553) ## Description - Create a celery task namespace for the workflow engine tasks - Create a task for processing an activity in the workflow_engine -- this will allow us to create a celery task to async execute process workflows when the issue platform creates an activity In the code I mention there being a follow-up PR: #93580 is the initial PR to support the `Activity` / `Group` models.
…move the 'group' to be a top level attribute, and change 'event' to be either Activity | GroupEvent
…strongly tied to events. in those cases, we should fail the condition
…instead of manipulating a frozen dataset
saponifi3d
force-pushed
the
jcallender/aci/support-activity-events
branch
from
c9847a3 to
58289a4
Compare
andrewshie-sentry
pushed a commit
that referenced
this pull request
Jun 19, 2025
…93553) ## Description - Create a celery task namespace for the workflow engine tasks - Create a task for processing an activity in the workflow_engine -- this will allow us to create a celery task to async execute process workflows when the issue platform creates an activity In the code I mention there being a follow-up PR: #93580 is the initial PR to support the `Activity` / `Group` models.
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
Since so much of the system needs access to the
WorkflowEventData.event.groupand theActivitymodel doesn't support it (but we do have access to it), so i movedgroupto the top level ofWorkflowEventData-- this allows a majority of the DataConditions to work seamlessly between activities and events.The core change here is to
WorkflowEventDatatype and everything else is a cascade that needed to be updated. Thanks to all for typing things so well to make this easier to discover / update.I'll have another PR that starts to send the activities and connects everything in
workflow_engine/tasks.py.