Opened 13 years ago
Closed 8 years ago
#10698 closed defect (worksforme)
Workflow action with non-ascii letters fails to change owner properly
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.12-stable |
| Severity: | normal | Keywords: | workflow, ticket, owner |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi,
Consider the two workflow actions below :
[ticket-workflow] reassign = * -> * reassign.operations = set_owner,leave_status reassign.set_owner = client,po,team todo = * -> todo todo.operations = set_owner todo.set_owner = client,po,team
If i set the owner with reassign action, it works well, as expected.
If i use the toto action, the owner is set to client,po,team literally, even if i select properly client.
Trac should set the status to todo and the owner to the one selected.
Can you confirm this ?
Regards, Étienne
Attachments (0)
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Summary: | Changing status and owner from an enum fails → Workflow action with non-ascii letters fails to change owner properly |
|---|
comment:3 by , 13 years ago
You shouldn't use non-ASCII characters in workflow option names. Instead, you should set the .name option to localize the action. So in this case:
[ticket-workflow] reassigner = * -> * reassigner.name = réassigner reassigner.operations = set_owner,leave_status reassigner.set_owner = client,po,team
Does everything work fine with ASCII-only option names?
follow-up: 5 comment:4 by , 13 years ago
Thanks for the answer.
Yep, i used the .name field, and it works properly. Thanks.
Would be nice if trac complains or ignore actions with non-ASCII letters. That's strange for a behaviour, to assign owner to all items !
Would a patch to prevent wrong action name be welcome ?
Regards, Étienne
comment:5 by , 13 years ago
| Milestone: | → unscheduled |
|---|
Replying to anonymous:
Would a patch to prevent wrong action name be welcome ?
Sure, patches are always welcome. Either log a warning when non-ASCII characters appear in action keys, or fix the workflow code so that it works correctly with such keys.
comment:6 by , 8 years ago
| Milestone: | unscheduled |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Tested with 1.2-stable and could not reproduce using the configuration in comment:1. I guess it's been fixed by now.



Hi,
Actually, the bug occurs when the action contains non ascii letter.
The
set_owneroperation fromréassigneraction will set owner toclient,po,team.Regards, Étienne