IssuesUsages
Represents a list of IssueUsage entities.
Field | Data type |
|---|---|
|
|
|
|
|
|
Below, you can find a full schema of this object, in XML and JSON formats. You can choose what fields to submit depending on your current needs. Different methods might expect different fields: the best approach is to request this entity via GET and use the response as a base for the following POST request.
A link to another object implies that you can substitute it with the schema of the linked object, if it is required for your call.
XML
JSON
<issuesUsages count="123" href="string">
<issueUsage>IssueUsage...</issueUsage>
</issuesUsages>{
"issueUsage" : [ {
"issue" : {
"id" : "id",
"url" : "url"
},
"changes" : {
"change" : [ {
"date" : "date",
"vcsRootInstance" : "vcs-root-instance...",
"canEditComment" : true,
"personal" : true,
"storesProjectSettings" : true,
"type" : "type",
"version" : "version",
"snapshotDependencyLink" : "SnapshotDependencyLink...",
"webUrl" : "webUrl",
"registrationDate" : "registrationDate",
"files" : "fileChanges...",
"parentRevisions" : "items...",
"internalVersion" : "internalVersion",
"comment" : "comment",
"attributes" : "properties...",
"id" : 6,
"href" : "href",
"user" : "user...",
"commiter" : "commiter...",
"locator" : "locator",
"parentChanges" : "changes...",
"username" : "username",
"status" : "ChangeStatus..."
} ],
"count" : 0,
"prevHref" : "prevHref",
"href" : "href",
"nextHref" : "nextHref"
}
} ],
"count" : 2,
"href" : "href"
}