Versions Compared

Old Version 1

changes.mady.by.user Kurt Wagner

Saved on

compared with

New Version Current

changes.mady.by.user Kurt Wagner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellow
titleUNDER DEVELOPMENT

Progressions allow your team to intelligently move records between statuses. The Public API currently supports automatic progressions, which skip over details requiring user interaction.

To perform an automatic progression you should:

  1. Determine what status progressions are available for the given object by hitting the get resource progressions endpoint. For example
Code Block
GET /issues/200/progressions.json
  1. By looking at the title and status details, determine the appropriate progression for your action. Keep track of the progression's id.
  2. Update the resource by posting the auto-progression ID to the auto progression endpoint for the resource.
Code Block
POST /issues/200/progressions/100/auto.json

[table of available progression endpoints]The API currently supports the following progression resources:

  1. tasks
  2. companies
  3. jobs
  4. prospects
  5. issues
  6. milestones
  7. affiliations
  8. contracts
  9. contacts
Info
titleProgression Permissions
For a user to perform an interaction on a progression they MUST have the process permission or be a manager (or assignee for tasks) of the object. The list progression actions endpoint will NOT return progressions on objects that do not meet these requirements.

Endpoints

METHODENDPOINTDESCRIPTION
GET/:resource/:resource_id/progressionsReturns an array of available progression actions. An ID from this response can be used to progress the object to the specified status.
[PUT|POST]/:resource/:resource_id/progressions/:progression_id/autoAutomatically progresses the resource to the progressions next status if applicable. The updated resource is returned upon success.

For more information, please click on the endpoint's links. Tasks also offer special progression endpoints that can be used in conjunction with these.

Sample

To perform an automatic progression you should:

1. Determine what status progressions are available for the given object by hitting the list resource progressions endpoint. For example

Code Block
languagexml
titleGET /issues/200/progressions.json
<data>
  <meta message="Everything executed as expected." more_info="https://affinitylive.jira.com/wiki/display/APIS/Status+Codes#ok" status="ok"/>
  <response id="133" title="New Ticket">
    <status id="2" color="yellow" standing="open" title="Open"/>
  </response>
  <response id="139" title="Close Ticket">
    <status id="4" color="blue" standing="closed" title="Closed"/>
  </response>
  <response id="140" title="Waiting For Client">
    <status id="6" color="orange" standing="open" title="Waiting for Client"/>
  </response>
</data>

2. By looking at the title and status details, determine the appropriate progression for your action. Keep track of the progression's id. In this case, we want to run "New Ticket" Progression #133.

3. Update the resource by posting the auto-progression ID to the auto progression endpoint for the resource.

Code Block
languagexml
titlePOST /issues/200/progressions/133/auto.xml
<data>
  <meta message="Everything executed as expected." more_info="https://affinitylive.jira.com/wiki/display/APIS/Status+Codes#ok" status="ok"/>
  <response id="200" title="Billing Issues Monthly to 3rd Party (Google)">
    <status id="2" title="Open"/>
  </response>
</data>