-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 7.6.0
-
Component/s: REST API
-
7.06
-
1
-
Severity 3 - Minor
-
0
Problem Definition:
If we run an example of GET REST Call towards JIRA below, Issue Type field would not have Operation Items:
<JIRA Base URL>/rest/api/2/issue/createmeta?projectKeys=JRA&issuetypeNames=Bug&expand=projects.issuetypes.fields
Expected Results
REST API docs mention the following (from https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1)
"issuetypes": [
{
"self": "http://www.example.com/jira/rest/api/2/issueType/1",
"id": "1",
"description": "An error in the code",
"iconUrl": "http://www.example.com/jira/images/icons/issuetypes/bug.png",
"name": "Bug",
"subtask": false,
"fields": {
"issuetype": {
"required": true,
"name": "Issue Type",
"hasDefaultValue": false,
"operations": [
"set"
]
...
Actual Results
Instead you get (result from JIRA - createmeta ):
issuetypes: [
{
self: "https://jira.atlassian.com/rest/api/2/issuetype/1",
id: "1",
description: "A problem which impairs or prevents the functions of the product.",
iconUrl: "https://jira.atlassian.com/secure/viewavatar?size=xsmall&avatarId=51493&avatarType=issuetype",
name: "Bug",
subtask: false,
expand: "fields",
fields: {
...
issuetype: {
required: true,
name: "Issue Type",
hasDefaultValue: false,
operations: [ ],
allowedValues: [
Note that operations is empty.
Suggested Solution
With the information in our documentation below, it is still possible to create an issue with setting the Issue Type using "Name" or "Id" but, since it is still possible, the opeartion items should mentioend "set" at least.
Update the createMeta result for Issue Type to include "set"