Edit Resolution without triggering an action
![]()
Hi,
I would like to know if there is a way to update or edit the "resolution" of a work item without triggering a new "workflow action". I have a custom workflow where I want user to be able to change the resolution without moving to the next state but the presentation in the web UI is disabled by default and user needs to change a new action for it to be able to change the resolution. Just to clarify what I'm trying to do: In Progress -> (Resolution A, Resolution B, Resolution C) Invalid -> (Resolution D, Resolution E) Complete -> (Resolution A, Resolution B, Resolution C) When the work item is in "In progress" state, I want him to be able to change the resolution between A, B or C, but I cant seem to do that at the moment. I also tried using a dependent enumeration instead of using built-in resolution, but couldn;t get that to work either. Any ideas or suggestions? |
Accepted answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Mar 20 '15, 8:16 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As far as I can tell, this is not possible. The resolution in that presentation is a non attribute based presentation. I was also not able to show the resolution as a normal property which would have allowed to show it in an additional presentation.
I think what you try to do does maybe not make such much sense in the context of a RTC workflow. The resolution as I understand it is really implemented to be used in the final closed state(s), where the reason for resolving (closing) the work item is chosen. You should consider if you want to add a custom enumeration that provides the information independent from the resolution (of the workflow). Neeraj Laad selected this answer as the correct answer
Comments Thanks Ralph and Sam.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As I already mentioned above, I don't see a way to do that.
Thanks Ralph
|
One other answer
![]()
No. This is not how the system works. Resolutions can only be set on state changes. They act like a dependent enum, but are handled with special code.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.