Item565: Adjusting State using Ajax can corrupt the status in case non-standard values are used.
Priority: Normal
Current State: No Action Required
Released In:
Target Release: n/a
Applies To: Engine
Component:
Branches:
If a user defines extra states for the
ActionTrackerPlugin and then tries to change the status via the Ajax interface, the status gets corrupted.
I have defined (See bold red characters for the interessant part)
* Set ACTIONTRACKERPLUGIN_EXTRAS = |said,text,8|mgate,select,1,"M13","M12","M11","M10","M9","M8","M7","M6","M5","M4","M3","M2"|deliverable,text,30|
state,select,1,"N/A","Not Planned","Planned","Assigned","Started","Ongoing","Reviewed","closed"|review,select,1,"No","N/A","FTR","Consensus"|evidence,text,50|
And uses this format to display actions defined:
%ACTIONSEARCH{ topic="Item565" mgate="M7" format="| $edit | $deliverable | $who | $state | $due | $review | $evidence | $text | $said |" header="| Update | Deliverable | Assigned to | Status | Due date | Review | Evidence URL | Comments | SA2006
ID |" orient="columns" }%
If I, in display mode, select a status and change it via the Ajax interface, the status defaults to my defined value "N/A".
Best regards
JC
--
TWiki:Main/JanCarstenJ - 15 Dec 2008
I am closing this, as it's a duplicate of
Item566
--
SeanMorgan - 05 Jan 2009