When trying to generate a new Jira Issue with a Parent Link as a 'default' parent for all submissions, I receive the below error. I'm unsure why it appears this way as I believe that the field needs to be part of the Create screen of the Project & Issue type which it is.
Any help would be appreciated:
Error:
Could not complete request (Create JIRA Issue) using configuration id = 349f9875-f286-443f-afcf-8f3c506a1dc8. Requested to https://nbnco.atlassian.net/rest/api/2/issue/ has resulted in error. Response code = 400. Response contents: {"errorMessages":[],"errors":{"customfield_10138":"Field 'customfield_10138' cannot be set. It is not on the appropriate screen, or unknown."}}
Code
"customfield_10138" : "ZZZNBNCNS-1070",
XML Pull from an issue with parent associated
<parent id="3140846">ZZZNBNCNS-1070</parent>
Do you have the field customfield_10138 available in the Jira issue create screen?
Try doing the following request (in a browser)
https://<your_server>.atlassian.net/rest/api/2/issue/createmeta?projectKeys=<your_project>&expand=projects.issuetypes.fields
Do you see this field in the response?
Hi Alex, I believe so yes. When I select Create Issue, Epic, near the bottom of the create screen I have the below:
As for the URL you asked me to open, It shows a very long screen of code. What should I be looking for?
Does this help you understand if it's showing correctly/not?
"name":"Epic","untranslatedName":"Epic","subtask":false,"hierarchyLevel":1,"expand":"fields","fields":{"customfield_15282":{"required":false,"schema":{"type":"string","custom":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","customId":15282},"name":"Risk & Cost of doing nothing","key":"customfield_15282","hasDefaultValue":false,"operations":["set"]},"parent":{"required":false,"schema":{"type":"issuelink","system":"parent"},"name":"Parent","key":"parent","hasDefaultValue":false,"operations":["set"]},"customfield_15283":{"required":false,"schema":{"type":"string","custom":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","customId":15283},"name":"Negative Impacts","key":"customfield_15283","hasDefaultValue":false,"operations":["set"]},"issuetype":{"required":true,"schema":{"type":"issuetype","system":"issuetype"},"name":"Issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Searching for "customfield_10138" field, as this is what gets reported to you as the one that does not exist on the Jira create screen, but you are sure it does exist.
So, let's verify that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Doesn't look like it's there somehow even though it's on the Create screen itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, what makes you think the "customfield_10138" is the name of the Epic field in Jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Alex, the Parent information in the XML of an EPIC shows as below. This is why I believe that 10138 is the 'parent' field for our instance:
<customfield id="customfield_10138" key="com.atlassian.jpo:jpo-custom-field-parent">
<customfieldname>Parent Link</customfieldname>
<customfieldvalues>
<customfieldvalue>
<![CDATA[ ZZZNBNCNS-1070 ]]>
I did also find this line, let me know your thoughts:
<parent id="3140846">ZZZNBNCNS-1070</parent>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure I understand this XML thing...
Could you please open a support ticket with us so we can look at it together
Will be great to see the response of the
https://<your_server>.atlassian.net/rest/api/2/issue/createmeta?projectKeys=<your_project>&expand=projects.issuetypes.fields
as text (in the private ticket you will open)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.