Auto Owner assignment according type
Accepted answer
Antoine,
you could use a script based calculated value provider, if you have a fixed list of types and users.
In the value provider you would read the type attribute and then return the UUID of the user you want. See https://jazz.net/wiki/bin/view/Main/AttributeCustomization and https://jazz.net/library/article/1093 for some hints.
If the association is not trivial and you need to search you could try https://rsjazz.wordpress.com/2013/06/26/attribute-customization-java-based-value-providers-conditions-and-validators/ .
Other viable approaches would be follow up actions / participants.
However: Why are there so few default value providers?
The reason is simple, when the work item is created and the providers run, there is almost no information available. Even the type is only preliminary and could be changed afterwards. That is the reason why default values as described by you don't really seem to make a lot of sense. The decision point for the value is after the fact of running the default value provider.
With Dashboards and queries, RTC provides way better ways to handle incoming work as well. The responsible persons would just have a query that shows them the unassigned work.
you could use a script based calculated value provider, if you have a fixed list of types and users.
In the value provider you would read the type attribute and then return the UUID of the user you want. See https://jazz.net/wiki/bin/view/Main/AttributeCustomization and https://jazz.net/library/article/1093 for some hints.
If the association is not trivial and you need to search you could try https://rsjazz.wordpress.com/2013/06/26/attribute-customization-java-based-value-providers-conditions-and-validators/ .
Other viable approaches would be follow up actions / participants.
However: Why are there so few default value providers?
The reason is simple, when the work item is created and the providers run, there is almost no information available. Even the type is only preliminary and could be changed afterwards. That is the reason why default values as described by you don't really seem to make a lot of sense. The decision point for the value is after the fact of running the default value provider.
With Dashboards and queries, RTC provides way better ways to handle incoming work as well. The responsible persons would just have a query that shows them the unassigned work.
One other answer
Hi ralph,
Thanks,
Antoine
Thanks for your answer. It's very appreciated.
Just one more thing.What do you mean by a script that also returns the user UUID ?
It's possible to get the user UUID in my script, according the name by example ?
Thanks,
Antoine
Comments
