Skip to end of metadata
Go to start of metadata

In the ALM configuration for Jira you can define fields which should be filled out whenever a new issue gets created from the piplanning app.

This is most usable in two scenarios:

  • Multiple teams are using the same Project. They only differentiate the issues via a Team field.
  • There are fields which are mandatory and have to be filled out every-time a new issue gets created.

The values have to be defined in a JSON fashioned style.

How to find out the field-id / key of a field

See here: How to get customfield-id (key) of a Jira field

Syntax examples for field type labels

{"<label-field-id>": ["label-one", "label-two"]}
{"customfield_10304": ["PiedPiper"]}

Labels can not have spaces. If they have spaces they will appear as individual labels

Syntax examples for field fixVersion

{"fixVersions": [{"name":"<Version-name>"}]}
{"fixVersions": [{"name":"1.4"}]}

Syntax example for components

{"components": [{"name":"Update"}]}

Syntax examples for field type Text-Field single-line

{"customfield_10305":"My text"}

 

Syntax example for field type Select List (single choice)

{"customfield_10306": {"value": "TeamA"}}


Syntax example for field type Select List (multiple choice)

{"customfield_11803":[{"value":"TeamA"}]}
or
{"customfield_11803":[{"value":"TeamA"}, {"value":"TeamB"}]}


Syntax examples for combining multiple fiels

{"customfield_10304": ["PiedPiper"], "fixVersions": [{"name":"1.4"}]}

 

 

Further explanations can be found here: https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#editing-an-issue-examples

 

  • No labels