File an issue
Files a new issue on the organization's board. Search first and update an existing issue instead of filing a duplicate; this call never matches existing issues.
Request
- Base URLhttps://docs.grepr.ai (the document declares no server; this is the origin it was published from)
- Auth
- API key in header GREPR-API-KEY
- or OpenID Connect (https://grepr-prod.us.auth0.com/.well-known/openid-configuration)
Request body
How sure the reporter is that the problem is real.
The current understanding, in markdown, or null for none.
The entity:* tags it concerns; an unprefixed key is put in the entity: namespace. Keys are stored in lower case, and values as given; searches match both in any case.
When the issue stops applying.
An optional free-form key for exact-match search.
Categories; reuse the labels search reports as in use.
The concrete next action and who it waits on.
How soon someone should act; agents must set it. A person who leaves it null files at P2, unlocked, so triage can set it.
When someone should check back.
The open state to file it in; null files it in TRIAGE. Agents may file only in TRIAGE, or READY when their handoff mode allows it.
The teams that may see it; people only, from the teams they can edit issues of (any for an organization-wide person). Absent: a team-scoped person's own teams, and none for an organization-wide person, which keeps the issue to organization-wide users.
One line naming the problem, not the symptom's timestamp.
Response
Issue filed
When it closed, or null while open.
How sure the reporter is that the problem is real.
When it was filed.
The current understanding, in markdown, kept current rather than appended to.
The surviving issue, set exactly when resolved as DUPLICATE; null in a response when the reader can't see the survivor.
True in a response whose reader can't see the surviving issue.
The entity:* tags it concerns, the same vocabulary as memory tags, keys in lower case, sorted by key.
When the issue stops applying and closes as EXPIRED, or null.
An optional free-form key for exact-match search, or null.
The first sighting, or null before any.
The issue id.
Categories, such as cost, sorted.
The latest sighting, or when it was filed.
The concrete next action and who it waits on, or null.
The short per-organization handle, shown as #142.
How many investigations sighted it.
How soon someone should act.
Whether it reopened on a new sighting after being fixed; cleared on its next close.
Why it closed; set exactly when state is CLOSED.
When someone should check back, or null. Then a Monitoring issue's watcher is started on it, or, with no watcher, it goes back to READY.
Where the issue is in its lifecycle.
When the state last changed.
The teams that may see the issue, sorted.
One line naming the problem.
When it last changed.
Bumped by every change to a field, the state, an assignment, a lock or the teams.
The agent watching it in MONITORING: the one that moved it there, started on it again when a sighting comes in or its revisit time passes. Null outside Monitoring.
Changes
No recorded changes to this operation across all 1 revision of this API.