JIRA REST API call for create issue of issuetype "Minutes"

[Arjun]

why JIRA looks into issue screen of type "BUG" by default while I attempt to create issue of type "MINUTES"?

Our organization has different screens for a bug and a minute.

while calling the create issue rest api call(to create minutes) it expects the fields in the bug.

Is this a bug or am I doing something wrong?

[Arjun · Accepted solution]

My Jira Admin just said they used a common config for issue, minutes and bug. Now they have split it(removed the mandatory field for Brands and Detection) and it works for me now.

[Robert Wen_ReleaseTEAM_ · Accepted solution]

Hello @Arjun .

What's the default issue type that is set for your Jira project?

[Arjun]

Hello @Robert Wen_ReleaseTEAM_ 

sorry, I'm not aware(where can I check that?). I usually clone a minute during new SW release.

When I tried from rest api call it defaults to bug screen. Also, there is no official version of clone rest call in jira.

[Robert Wen_ReleaseTEAM_]

In Jira Server, default issue types can be set.  If you don't specify an issue type (like Minutes), it will set the issue type to the default.

Are you setting issue type in your REST call?  It is one of the fields that you can define.

[Arjun]

Please see below the request that has issuetype set.

curl -i -v -u user:password --data "{\"fields\": { \"project\": { \"key\": \"ABC\" }, \"summary\": \"My sample mins\", \"description\": \"sample mins\", \"issuetype\": { \"name\": \"Minutes\" }}}" -H "Content-Type: application/json" "https://url.com:123/rest/api/2/issue/"

output

{"errorMessages":["Brands: Brands is required.","Detection: Detection is required."],"errors":{"components":"Component/s is required."}}

The field "Brands" and "Detection" belongs to bug screen and not minutes.

Edit: I just now checked in jira --> project-settings --> screens and see that default is minutes. I could see the "default" tag and below that Minutes is mentioned.

[Arjun]

@Robert Wen_ReleaseTEAM_:

when I try to create bug(id - 1) it says custom fields are missing in the  response but when the same is tried with minutes(id - 12), the output has the custom field names(Brands and Detection) instead of 'customfield_xxxxx'. do you think something is wrong in the Jira settings?

D:\scripts>curl -u user:password --data "{\"fields\": { \"project\": { \"key\": \"ABC\" }, \"summary\": \"my sample bug\", \"description\": \"sample bug\", \"versions\": [{\"Affects Versions/s\": \"v1.2\"}, {\"name\": \"v1.2\"}], \"issuetype\": { \"id\": \"1\", \"name\": \"Bug\" }, \"components\": [{\"name\": \"SW_VERSION\"}]}}" -H "Content-Type: application/json" "https://someurl.com:123/rest/api/2/issue/"

{"errorMessages":[],"errors":{"customfield_10393":"Brands is required.","customfield_10142":"Defect Occurrence is required.","customfield_13310":"Detection is required.","customfield_10390":"Relevance is required.","customfield_10322":"Basket is required."}}

D:\scripts>curl -u user:password --data "{\"fields\": { \"project\": { \"key\": \"ABC\" }, \"summary\": \"my sample mins\", \"description\": \"sample mins\", \"versions\": [{\"Affects Versions/s\": \"v1.2\"}, {\"name\": \"v1.2\"}], \"issuetype\": { \"id\": \"12\", \"name\": \"Minutes\" }, \"components\": [{\"name\": \"SW_VERSION\"}]}}" -H "Content-Type: application/json" "https://someurl.com:123/rest/api/2/issue/"

{"errorMessages":["Brands: Brands is required.","Detection: Detection is required."],"errors":{}}

[Robert Wen_ReleaseTEAM_]

@Arjun . You look like you're doing everything right, so I need to ask some specifics:

What version of Jira are you running?

What type of project is this? (Core, Software, Service Desk/Management?)

[Arjun]

@Robert Wen_ReleaseTEAM_  Jira Server v8.20.3. This is for Software. We mostly use issue types Bug, Minutes, Task and Sub task. Please hold, as I'm currently checking with my Jira Admin as I get the same error while I attempt to create a minute manually in Jira web.

[Robert Wen_ReleaseTEAM_]

OK, this makes sense.  Sounds like there was a change in the field configuration that affected the Meetings issue type (perhaps other ones too).

[Arjun]

@Robert Wen_ReleaseTEAM_I'm really sorry for wasting your time. My Jira Admin just said they used a common config for issue, minutes and bug. Now they have split it(removed the mandatory field for Brands and Detection) and it works for me now.

[Sherif Hikal]

Well Done, it seems like the issue has been resolved. 

configuration, debug and needed little brushing to e ready for prime time.

Not much to get it up and running at tip-top shape.