-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename instances of Zeebe user task
to Camunda user task
#4749
Comments
Skaiir
added a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Dec 11, 2024
barmac
pushed a commit
to camunda/linting
that referenced
this issue
Dec 12, 2024
barmac
pushed a commit
to camunda/linting
that referenced
this issue
Dec 12, 2024
barmac
pushed a commit
to camunda/linting
that referenced
this issue
Dec 12, 2024
barmac
pushed a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Dec 12, 2024
barmac
pushed a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Dec 12, 2024
This is now fixed upstream. |
barmac
added
fixed upstream
Requires integration of upstream change
and removed
in progress
Currently worked on
labels
Dec 12, 2024
4 tasks
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
fixed upstream
Requires integration of upstream change
labels
Dec 13, 2024
nikku
pushed a commit
that referenced
this issue
Dec 13, 2024
nikku
pushed a commit
that referenced
this issue
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should we do?
We should rename all textual instances of
Zeebe user task
toCamunda user task
. We do not have to change how they are defined in the code however.What this comes down to in practice is that we need to change:
camunda/linting
message instances that include zeebe user taskWhy should we do it?
This is a company wide renaming of the user task type.
The product hub epic is here: https://github.com/camunda/product-hub/issues/2126 and decisions are traceable there if you're interested.
The text was updated successfully, but these errors were encountered: