Why does work item save silently reject change of status ?
Scenario: RTC 5.0.2 ifix006. Defect work item type with spaget, er elaborate workflow. One defect in particular when attempting to move from the current status to In Progress quietly allows a save but does not actually make the change. When using ?debug=true, saving and looking at the work item history this is displayed:
For the In Progress status, no resolutions are enabled ( which I believe is the norm ). Watching the web UI activity with Firebug I see this message following a POST
[Value Conversion]: could not interpret [object Object] as a string. Returning as empty string.
I tracked the project change history and work flow not touched since this particular work item was created. I also checked workflow usage and attribute usage. Workflow ok, lots of work items with missing attributes.
For the In Progress status, no resolutions are enabled ( which I believe is the norm ). Watching the web UI activity with Firebug I see this message following a POST
[Value Conversion]: could not interpret [object Object] as a string. Returning as empty string.
I tracked the project change history and work flow not touched since this particular work item was created. I also checked workflow usage and attribute usage. Workflow ok, lots of work items with missing attributes.
Comments
Donald Nong
Nov 20 '15, 3:40 a.m.Kevin Ramer
Nov 20 '15, 7:51 a.m.Kevin Ramer
Nov 20 '15, 9:05 a.m.Donald Nong
Nov 22 '15, 7:49 p.m.Kevin Ramer
Nov 24 '15, 9:13 a.m.