Ticket Associations Fields


To fetch metadata of Ticket Association object send a GET request to:

https://api.assembla.com/v1/meta/ticket_associations.(json|xml)

example. request json with curl utility:

curl -H "Authorization: bearer _token" https://api.assembla.com/v1/meta/ticket_associations.json

example. request xml with curl utility:

curl -H "Authorization: bearer _token" https://api.assembla.com/v1/meta/ticket_associations.xml

table below is the list of fields contained in the response, this list will be properly formatted to json or xml as requested.

Fields

Param Data type Access Description
id integer read Ticket association id
ticket1_id integer read ID of first ticket in association, this is generaly taken from the URL params, not required in request data bodies.
ticket2_id integer read ID of second ticket in association
relationship integer read/write Relationship of association, integer values are in bold:
  • 0 - Parent
  • 1 - Child
  • 2 - Related
  • 3 - Duplicate
  • 4 - Sibling
  • 5 - Story
  • 6 - Subtask
  • 7 - Dependent
  • 8 - Block

Explanation on relationships:

  • relationship is 0 - ticket2 is parent of ticket1 and ticket1 is child of ticket2
  • relationship is 1 - ticket2 is child of ticket1 and ticket2 is parent of ticket1
  • relationship is 2 - ticket2 is related to ticket1
  • relationship is 3 - ticket2 is duplication of ticket1
  • relationship is 4 - ticket2 is sibling of ticket1
  • relationship is 5 - ticket2 is story and ticket1 is subtask of the story
  • relationship is 6 - ticket2 is subtask of a story and ticket1 is the story
  • relationship is 7 - ticket2 depends on ticket1
  • relationship is 8 - ticket2 blocks ticket1

Validations

No validations available