associated workflow execution with cron-trigger
Bug #1684482 reported by
int32bit
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Won't Fix
|
Low
|
int32bit | ||
Bug Description
If the workflow execution was created by a cron, our client may want to know which cron event triggered it. What's more, our user may also want to list workflow execution by cron instance. A simplest way is to add cron name/id to workflow execution description.
| Changed in mistral: | |
| assignee: | nobody → int32bit (int32bit) |
| Changed in mistral: | |
| milestone: | none → pike-2 |
| importance: | Undecided → Low |
| Changed in mistral: | |
| status: | New → In Progress |
Revision history for this message
| Renat Akhmerov (rakhmerov) wrote | #1 |
| Changed in mistral: | |
| milestone: | pike-2 → pike-3 |
Revision history for this message
| Sharat Sharma (sharat-sharma) wrote | #2 |
| Changed in mistral: | |
| status: | In Progress → New |
Revision history for this message
| Renat Akhmerov (rakhmerov) wrote | #3 |
Revision history for this message
| Andras Kovi (akovi) wrote | #4 |
Revision history for this message
| Nikolay Makhotkin (nmakhotkin) wrote | #5 |
| Changed in mistral: | |
| status: | New → Won't Fix |
| Changed in mistral: | |
| milestone: | pike-3 → none |
To post a comment you must log in.
I think it is rather a blueprint than a bug. It's a matter of adding some contextual info (maybe as part of workflow environment) to the workflow execution. I'd suggest you close this bug and file a BP.