Return repository data

get

/*/issues/issues/v2/repository

Data that is returned consists of the collections of allowed values for the fields in an issue.

Request

Query Parameters
fields
Type: string
A comma-separated list of the names of the fields to return.

Response

200 Response
successful operation
Body
Root Schema : Repository
Type: object
Nested Schema : components
Type: array
Nested Schema : configurationProperties
Type: object
Nested Schema : customFields
Type: array
Nested Schema : Priority
Type: object
Nested Schema : Product
Type: object
Nested Schema : Resolution
Type: object
Nested Schema : Severity
Type: object
Nested Schema : Status
Type: object
Nested Schema : priorities
Type: array
Nested Schema : products
Type: array
Nested Schema : releases
Type: array
Nested Schema : resolutions
Type: array
Nested Schema : searches
Type: array
Nested Schema : severities
Type: array
Nested Schema : stateTransitions
Type: array
Nested Schema : statuses
Type: array
Nested Schema : tags
Type: array
Nested Schema : types
Type: array
Nested Schema : users
Type: array
Nested Schema : Component
Type: object
Nested Schema : User
Type: object
Nested Schema : FieldDescriptor
Type: object
Nested Schema : values
Type: array
Nested Schema : CustomFieldValue
Type: object
Nested Schema : components
Type: array
Nested Schema : releases
Type: array
Nested Schema : releaseTags
Type: array
Nested Schema : ReleaseTag
Type: object
Nested Schema : Release
Type: object
Nested Schema : SortInfo
Type: object
Nested Schema : StateTransition
Type: object
Nested Schema : Tag
Type: object

Examples

The following example shows how to submitting a POST request on the REST resource using cURL to retrieve metadata about the “status” issue property from the repository that stores all information about all issue properties. The example uses the “field=3D” URL query parameter to restrict returned data to fields for statuses only. For more information about cURL, see Use cURL. For more information about endpoint URL structure, see Send Requests.

curl -i
-X GET 
-s http://developer.us.oraclecloud.com/dev-org/rest/dev-org_pubapi_203132/issues/v2/repository?fields="statuses"

Example of Response Header

The following shows an example of the response header.

200 Successful Operation
Content-Type: application/json
Date: Thu, 17 Aug 2017 00:26:10 GMT

Example of Response Body

The following example shows the contents of the response body in JSON format. Notice that the content includes metadata about the “status” property only. Data is returned in a single line. The response has been formatted to improve readability.

{"repository":
  {"statuses":[
    {"id":1,"value":"UNCONFIRMED","isActive":true,"isOpen":true,"sortkey":100},
    {"id":2,"value":"NEW","isActive":true,"isOpen":true,"sortkey":200},
    {"id":3,"value":"ASSIGNED","isActive":true,"isOpen":true,"sortkey":300},
    {"id":4,"value":"REOPENED","isActive":true,"isOpen":true,"sortkey":400},
    {"id":5,"value":"RESOLVED","isActive":true,"isOpen":false,"sortkey":500},
    {"id":6,"value":"VERIFIED","isActive":true,"isOpen":false,"sortkey":600},
    {"id":7,"value":"CLOSED","isActive":true,"isOpen":false,"sortkey":700}
  ]
}}

The "fields=" query parameter can be used with queries made using issues and issues/<issue-id> resources as well.

You would use the status information that was retrieved from the repository to update the status of an issue.