Version 1.1
/Mobile/projects/milestones/edit
Inputs
Input | Input Definition | Required | Detailed Description |
tlid | The tasklist id | Yes | |
name | The new name for the tasklist | No | If you do not pass this parameter, it will retrieve what is in the database. |
desc | The new description for the tasklist | No | If you do not pass this parameter, it will retrieve what is in the database. |
mid The associated milestone id | No | If you do not pass this parameter, it will retrieve what is in the database. |
type | used to determine JSON or XML | No | If parameter is not passed than it will assume JSON. |
sid | The user's session id | Yes | If you do not pass a user session then no action can be taken. See the session debug section for disabling the session for debuging. |
While you can pass sid as GET parameter you are also welcome and recommended to pass it via POST for more security.
Ouputs
Response | Response Definition | Detailed Description |
statusCode | The status code for the returned result. (In this case should always be Success | |
statusMessage | The message that describes the associated status code. | |
id | The tasklist id | |
name | The name of the tasklist | |
description | The description of the tasklist | |
mid | The associated milestone | |
Sample Outputs
JSON
{"response":
{"status":
{"statusCode":"1",
"statusMessage":"Success!"},
"tasklist":
{"id":"1",
"name":"tasklist Name",
"desc":"The tasklist description",
"mid":"2"}
}
}
XML
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>
<statusCode>1</statusCode>
<statusMessage>Success!</statusMessage>
</status>
<tasklist>
<id>1</id>
<name>tasklistName </name>
<desc> The tasklist description </desc>
<mid> 2</mid>
</tasklist>
</response>