The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Field 'summary' cannot be set

Ben Arent
May 30, 2013

Hi there,

I'm trying to create an issue using Jira Rest API.
I'm trying to do that through the Airbrake service using our integration.
When sending, Jira API has returned:
Field 'summary' cannot be set. it is not on the appropriate screen, or unknown.

This is just happening for this account: https://gobalto.atlassian.net and user which this account belongs to told me that he has Summary field on his default screen scheme.
We are sending JSON like this:
{
"fields" => {
"project" => {
"key" => options[:project_key]
},
"summary" => title(options[:group]),
"issuetype" => {
"name" => "Bug"
},
"labels" => [
"airbrake"
],
"environment" => environment(options[:group]),
"description" => body(options[:group])
}
}
and like I said, this problem is just on that Jira account.
Thank you for your help

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
C_Faysal _CFcon_
Community Champion
May 30, 2013

Hey Ben. did that work before?

i guess since Jira 6 it shouldn't by default and i bet OnDemand uses 6 as well.

JSON-P no longer supported

JSON-P will not be supported in JIRA 6.0 for security reasons: it is possible for an attacker use this to view information in a JIRA instance that they do not have permission to see.


Ben Arent
May 30, 2013

Yes it worked before.
I'm on onDemand too (Atlassian JIRA v6.0-OD-14-WN) like this user and it's working perfectly for me.
What do you think?

Ben Arent
June 3, 2013

update please?

TAGS
AUG Leaders

Atlassian Community Events