0014945: Status workflow ignored

ID	Project	Category	View Status	Date Submitted	Last Update
0014945	Mylyn Connector	Core	public	2012-11-04 11:29	2012-11-04 12:15

Reporter	rombert	Assigned To
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	acknowledged	Resolution	open
Product Version	3.0.1
Target Version	Backlog

Summary	0014945: Status workflow ignored
Description	This is a major glitch. The listboxes that describe the Attributes ignore the set Status threshold directives defined in config_inc.php. This allows the user to set any status even if the workflow tries to restrict it. I mistakenly assigned an incident to New from acknowledged even when the workflow was set to $g_status_enum_workflow[ACKNOWLEDGED] = '20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved'; This is insane as I cannot enforce workflow. If possible it would be best if only those workflow states allowed for the user are shown as is the case on the web interface. Most importantly, any attempt to change the satatus to anything not allowed by the workflow should be rejected RE: set_status_threshold ignored By: Simon (simon_digital-d) - 2007-08-17 19:31 I could be mistaken, but shouldn't the webservice envorce threshold so the connector should not even recieve the values he has no access to? I assume it is configured correctly and works in the webtool? Probably its a problem with the webservice and not the connector but I see if I can take a look at this. Simon I completely agree and this works fine from the webtool if that's what you call the normal web inteface. I've installed Mantis 1.1.0a4 by copying the files from the archive over the mantis-1.0.7-1.fc5.noarch.rpm install. There is no problem using the service through the web browser. I installed MantisConnect-1.0a5/webservice into the mantis directory. It's named mc. I have created a task repository in eclipse and pointed it to the mc/mantisconnect.php url for my installation. I can see all my tasks and queries, it works fine. When I look at a task attributes, I see that all status options are allowed in the drop down list box. If I change the status from assigned to new, this is allowed. If I change it back to assigned this is also allowed. It seems to be configured correctly as it works fine through the web browser interface. It seems as if my mylyn doesn't function as expected. At this point I'm not sure what to add to the test server to test this. It will need a published workflow restriction and then simply a task which is in the restricted state.
Tags	No tags attached.

rombert 2012-11-04 11:29 manager ~0033515	As commented by whobe: This is definitely not a connector problem I can reproduce this in SoapUI I created a mantis task for this: http://www.mantisbt.org/bugs/view.php?id=8348 It's been there for over 6 months and nothing has been done on it. Perhaps if you add your support there it might get moving. Otherwise, I see mantis with mantisconnect to be broken since workflow can't be enforced.

rombert 2012-11-04 11:29 manager ~0033516	Original note author: kurtzarig What about a workaround: The mantis core offers the method "bug_check_workflow( $p_bug_status, $p_wanted_status )" which can be easily implemented in mantis-connect. When a bug is opened in the task-view one could check for every status defined in the enum $s_status_enum_string if the corresponding status is allowed in the workflow and display only the allowed ones.

rombert 2012-11-04 11:29 manager ~0033517	This is technically feasible, but I'd rather have a method call which retrieves all valid configurations, for performance reasons.

rombert 2012-11-04 11:29 manager ~0033518 Last edited: 2012-11-04 12:15	Originally reported at https://sourceforge.net/apps/mantisbt/mylyn-mantis/view.php?id=10 by rombert

View Issue Details

Activities