Note: Any mention of Iteration or Project in any Web Service operations are equivalent to Sprint or Board in the SwiftKanban User Interface (UI).

addCard

Input Elements

Description

Creates a new card

projectId

Id of the project that you get from getProject of ProjectService

Example: 8

cardType

Card type of the card obtained from getCardListForProject output

Example: UserStory

userLoginId

Email address of user to log on to SwiftKanban

Example:sam@digite.com

mode

Not used as of now

fields

List of fields with name and value for each field. Field name will be available from the getCardMetadata method. The type of value to be passed information will be available in the same method. If the field is of the list of value(LOV) type pass any relevantLOVitem value.

Sample of Invalid Output Response

Note: If you enter any invalid criteria in your input response (refer the above row), the output response will display error message instead of empty result. See the instances of error messages in the following response.

Email address of user to log on to SwiftKanban
Example: sam@digite.com

cardUniqueId

card unique id that you will get in add/update/get card response
Example: 5698

fields

List of fields with name and value for each field. Field name will be available from the getCardMetadata method. The type of value to be passed information will be available in the same method. If the field is of LOV type, pass any relevant LOV item value.
Example: name=cardSize and its value = L

Email address of user to log on to SwiftKanban
Example: sam@digite.com

fields

List of fields with name and value for each field. Field name will be available from the getCardMetadata method. The type of value to be passed information will be available in the same method. If the field is of LOV type, pass any relevant LOV item value.
Example: name=cardSize and its value = L

Email address of user to log on to SwiftKanban
Example: sam@digite.com

cardUniqueId

Card unique id that you will get in add/update/get card response
Example:606645

fields

List of fields with name and value for each field. Field name will be available from the getCardMetadata method. The type of value to be passed information will be available in the same method. If the field is of LOV type, pass any relevant LOV item value.
Example: name=cardSize and its value = L

Output

If successful, updates selected fields of the multiple cards passed in the request.

Email address of user to log on to SwiftKanban
Example: sam@digite.com

cardUniqueId

Card unique id that you will get in add/update/get card response
Example:606645

fields

List of fields with name and value for each field. Field name will be available from the getCardMetadata method. The type of value to be passed information will be available in the same method. If the field is of LOV type, pass any relevant LOV item value.
Example: name=cardSize and its value = L

Email address of user to log on to SwiftKanban
Example: sam@digite.com

cardUniqueId

fromQkeyId

toQkeyId

fromSwimId

toSwimId

Card unique id that you will get in add/update/get card response
Example:606645

Id of queue where the card exists nowExample:243566

Id of the queue to where you want to move the cardExample:567567

Id of the swim lane where the card exists nowExample:76867
Id of the swim lane to where you want to move the cardExample:123123 OutputIf successful, the cards are moved to the queue of the given swim lane

deleteMultipleCardInput Elements
Description Deletes particular cards on the boardprojectId Id of the project that you get from getProject of ProjectService
Example: 40218cardType Card type of the card obtained from the getCardListForProject output.
Example: UserStory

cardUniqueId Card unique id that you will get in add/update/get card response
Example: 606645

userLoginId Email address of user to log on to SwiftKanban
Example: sam@digite.com

Output If successful, deletes the particular cards on the boardInput Request Example

Relations need to be removed or not.
Consider the following scenario:
ENHC is linked to UST and TASK in card type links, but there is no link between DEF and UST.
Suppose ENHC10 is linked with UST20, and we are trying to convert
ENHC10 card to a Defect card type. Now
if breakRelation value set to true :
There will be no relation between UST20 and newly created target card DEF1.
if breakRelation value set to false :
Card conversion will fail

Suppose we are trying to convert ENHC10 to a TASK card type, then
as the relation is already defined between these two card types,
break relation parameter will be ignored and card will be converted.OutputIf successful, the response return converted card details.