Issues_ReopenIssues
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/issues:reopen';const options = { method: 'POST', headers: {'X-API-Key': '<X-API-Key>', 'Content-Type': 'application/json'}, body: '{"parent":"example","selection":{"names":{"names":["example"]},"filter":"example"}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/issues:reopen \ --header 'Content-Type: application/json' \ --header 'X-API-Key: <X-API-Key>' \ --data '{ "parent": "example", "selection": { "names": { "names": [ "example" ] }, "filter": "example" } }'Reopens dismissed issues scoped to the parent (same matching rule as DismissIssues). An episode a person ruled with a reopened issue becomes unreviewed again in that scope.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The dataset id.
Request Body required
Section titled “Request Body required ”Request for Issues.ReopenIssues.
object
Accounts/{account}/datasets/{dataset}
Which issues; only DISMISSED ones are reopened.
object
Issue names under the request’s parent.
object
Accounts/{account}/datasets/{dataset}/issues/{issue}, at most 10000.
A ListIssues filter over the parent, e.g. code = "idle_tail" AND state = OPEN.
Example generated
{ "parent": "example", "selection": { "names": { "names": [ "example" ] }, "filter": "example" }}Responses
Section titled “ Responses ”OK
Response for Issues.ReopenIssues.
object
How many issues were reopened.
Episodes whose issues were left as they were, because another person holds the episode’s edit lease. Their issues are not in reopened_count.
The first 100 of them, with their holders.
An episode a write left alone, or refused, because another person holds its edit lease (Episodes.AcquireEpisodeLease). Bulk responses list at most 100 of these beside a count of all of them.
object
Accounts/{account}/datasets/{dataset}/episodes/{episode}, in the scope the write was made in.
The holder’s display name; empty when they have none. (— api-linter: core::0122::name-suffix=disabled aip.dev/not-precedent: a person’s display name, as Episode.Lease calls it. —)
Example generated
{ "reopenedCount": 1, "lockedCount": 1, "locked": [ { "episode": "example", "holderName": "example" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}