Emma Thorpe
8c5773447e
Creating a WSP Task now fails with "Task Type is required to create a Task issue". The field is customfield_15622 and the create validator enforces it even though createmeta does not list it as required - the same trap the note already records for Bug's versions field.
4.1 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| jira-wsp-fields | WSP Jira project field map — issue-type IDs, required Bug fields with allowed values/IDs, and the Task shortcut for fast ticket creation |
|
Field map for the WSP (Workspace Platform) Jira project, to create tickets without trial-and-error. Site citrix.atlassian.net, cloudId 70cbc59a-06d2-4508-a9a6-61f1dbc2057f, project key WSP, project id 10061. See also jira-tooling.
Issue-type IDs: Epic 10000, Story 10004, Task 10008, Bug 10123, Sub-task 10009.
Fast path — use Task, not Bug. A Task requires summary plus Task Type customfield_15622 (added since this note was first written; the create validator enforces it even though createmeta omits it, same trap as Bug's versions). Options value=id: Dev Task=34065, CQE Task=34066, Investigation=34067, Security=34068, Maintenance=34069, Release=34070 — use Maintenance for refactors and tidy-ups, Dev Task for feature work. A Bug requires six extra fields (below), so only pick Bug when it must be a Bug. The sibling infra/remediation tickets in WSP are Tasks.
Example Task additional_fields: {"customfield_15622":{"id":"34069"},"components":[{"name":"Multicluster Platform"}]}
Bug required fields (enforced by the create validator; note createmeta omits versions but the API rejects without it):
| Field | Key | Shape | Allowed values (value = id) |
|---|---|---|---|
| Severity | customfield_10061 |
{"value":"S2"} |
S1=10643, S2=10644, S3=10645, S4=10646 |
| Affects Environment | customfield_10116 |
{"value":"Production"} |
Production=11031, Staging=11032, Integration=11033, Development=11034, Test=11035 |
| Defect Source | customfield_10138 |
{"value":"Internal - Manual"} |
Internal - Manual=12699, Internal - Automation=12700, Customer=12702, Security Review=12704 |
| Regression | customfield_10141 |
{"value":"No"} |
Yes - Previous Build=12705, Yes - Previous Release=12706, No=12707 |
| Components | components |
[{"name":"Workspace Configuration"}] |
109 options; relevant ones below |
| Affects versions | versions |
[{"name":"<version>"}] |
not in requiredFieldsOnly createmeta — fetch current list from full createmeta or project versions before setting |
Select customfields (...customfieldtypes:select) accept {"value":"..."} or {"id":"..."}. Components/versions accept [{"name":...}] or [{"id":...}].
Relevant Components (name=id): Workspace Configuration=12052, Workspace-Platform=12060, Multicluster Platform=12023, WSP Core Ingress=12037, Microservice Infrastructure=12020, Infrastructure=34375, Custom Domain Proxy=12021, Custom Domain Ingress Manager=11968, Custom Domain Infrastructure=11975, StoreFrontConfiguration=12042, StoreFront=12050, Test Infrastructure=12012, WSP Release Infrastructure=12011.
Other create notes: pass description/commentBody with contentFormat: markdown; set labels via additional_fields {"labels":[...]}; attach to an epic with the top-level parent param (parent: "WSP-32494" works for epic→Task). WSP transition IDs live in jira-tooling.
Example Bug additional_fields:
{"customfield_10061":{"value":"S2"},"customfield_10116":{"value":"Production"},"customfield_10138":{"value":"Internal - Manual"},"customfield_10141":{"value":"No"},"components":[{"name":"Workspace Configuration"}],"versions":[{"name":"<version>"}],"labels":["..."]}