View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0008348mantisbtapi soappublic2007-09-11 22:172011-10-27 05:26
Reporterwhobe Assigned To 
PrioritynormalSeverityblockReproducibilityalways
Status acknowledgedResolutionopen 
Product Version1.1.0a4 
Summary0008348: mantisconnect ignores g_status_enum_workflow
Description

Using the soapui I can change the status of an issue to anything. If there is a restriction in place it is ignored and the issue status is changed anyway. I'm using mc_issue_update. Also, it says that the project, summary and category are optional, but I always have to supply these.

In addition to this a request for mc_enum_status should have an optional parameter issue_id and return only those statuses valid for the workflow of this issue. This will maky my mylyn mantis connector useful. As it is I cannot allow anyone to use it or workflow would go out the window.

Steps To Reproduce

Restrict the workflow from a particular status.
Create and issue and set it in that state.
Use soapUi to modify the status into the restricted status.
Response:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<ns1:mc_issue_updateResponse xmlns:ns1="http://futureware.biz/mantisconnect">
<return xsi:type="xsd:boolean">true</return>
</ns1:mc_issue_updateResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Tagsrefactoring, soap api

Activities

vboctor

vboctor

2007-09-16 22:56

manager   ~0015647

The suggested change make sense. One of the reason MantisConnect is now part of Mantis is to gradually make sure that all business logic in Mantis is also used by MantisConnect. The cases where such business logic is not applied is mainly due to the business logic living in Mantis script pages rather than the API.

I also agree with adding the functionality of allow the retrieval of next possible statuses for a specific issue based on workflow rules.
urkle

urkle

2008-01-28 13:37

reporter   ~0016863

What work is required to get this issue resolved???
From what I've gathered it is

  • Add logic to bug API to enforce workflow
  • Add hooks to mantis-connect to inquire about workflow for an issue

This wouldn't really require any changes to the mantis script pages initially as it would just double enforce/check the workflow. Correct?
vboctor

vboctor

2008-01-30 03:27

manager   ~0016883

It will only require changes to the script if there is currently logic in the script pages which does the enforcement of the workflow. In this case, this code should be moved to the API and used from both the script page and the SOAP API.
JanHegewald

JanHegewald

2011-10-26 09:49

reporter   ~0030078

Hello,

are there any news concerning this issue? I have been trying Mylyn Mantis Connector and was suprised, that you can set every issue to any state.
rombert

rombert

2011-10-26 10:53

reporter   ~0030080

Well, no one cared that much to implement it. Would you be willing to contribute a patch?