Bug JSON Fields
Here are the bug fields tracked inside of Simscope:
| Field | Description | Example value |
|---|---|---|
title | Title of the bug | "This is my bug title" |
state | Bug State | "Closed" |
priority | Bug Priority | "High" |
project | Bug Project | "My Project"(this field is different from Simscope's project field) |
component | Bug Component | "My Component"(this field is different from Simscope's component field) |
branch | Bug Branch | "main" |
assignee_email | Bug Assignee Email | "john@company.com" |
reporter_email | Bug Reporter Email | "sally@company.com" |
created | Bug Creation Timestamp | "2021-10-06T20:41:09.279+00:00"(must be in RFC-3339 format |
updated | Bug Update Timestamp | "2021-10-06T21:42:10.279+00:00"(must be in RFC-3339 format |
resolved | Resolve Timestamp | "2021-10-07T12:44:48.7-05:00"Note: only set this field if the bug has been resolved |
Example Update JSON
This is an example JSON object for bug SIM-14
- Note this JSON does not have a
resolvedfield, because the bug is still active.
{
"title": "Simscope Signature 1244: FAIL verops oktaauth build failed: Oct 6.01, 2021",
"state": "To Do",
"priority": "Medium",
"project": "Simscope",
"component": "server",
"branch": "",
"assignee_email": "payton@verops.com",
"reporter_email": "infra@verops.com",
"created": "2021-10-06T20:41:09.279+00:00",
"updated": "2021-10-06T20:42:00.580+00:00"
}