board-github

PUT `/v1/board-github/links/{linkId}/items/{itemId}/field`

Set or clear one field value on a GitHub Project item.

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X PUT https://api.zinndigital.com/v1/board-github/links/{linkId}/items/{itemId}/field \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "field_node_id": <string> }'

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

`value: null` **clears** the field, through a different GitHub mutation. Sending an empty string would set the field *to* the empty string, which a date field refuses and a text field renders as a permanent blank chip — a save that looks like it worked. Only TEXT, NUMBER, DATE, SINGLE_SELECT and ITERATION are writable; every other type is either computed by GitHub or set on the underlying issue. The `writable` flag on each field in the connection payload is computed server-side so the UI never keeps its own copy of that list.

Cabiraha

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`linkId (path)`	`string`	Haa	The GitHub Projects connection.
`itemId (path)`	`string`	Haa	The item, by OUR id — not GitHub's node id, which is not a path-safe value.

Codsiga jidhkiisa

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`field_node_id`	`string`	Haa	—
`value`	`object`	Maya	`null` CLEARS the field, through a different GitHub mutation. An empty string would set the field to the empty string.

Jawaab

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`id`	`string`	Maya	—
`item_node_id`	`string`	Maya	—
`item_type`	`string<ISSUE, PULL_REQUEST, DRAFT_ISSUE, REDACTED>`	Maya	—
`content_number`	`integer`	Maya	—
`repository`	`string`	Maya	—
`title`	`string`	Maya	—
`body`	`string`	Maya	—
`url`	`string`	Maya	—
`state`	`string`	Maya	—
`is_archived`	`boolean`	Maya	—
`field_values`	`object`	Maya	Keyed by the field's node id, never its name. A project owner renaming a field would otherwise orphan every stored value at once, and the next sync would read it as "every i…
`github_updated_at`	`string`	Maya	—
`local_updated_at`	`string`	Maya	When WE last changed this item. Set only by a local edit, never by a sync — a sync that stamped it would make every imported item look locally-edited and hand every subsequent c…
`card_id`	`string`	Maya	—

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 422

PUT /v1/board-github/links/{linkId}/items/{itemId}/field