POST
{
"fields":
{
"project":
{
"key": "{{project}}"
},
"summary": "DEAP - {{summary}}"
,
"issuetype":
{
"name": "DEAP"
},
"versions":[
{"name":"{{affectversion}}"}
],
"assignee": {
"name":"{{Assignee}}"
},
"reporter":{
"name":"{{Reporter}}"
},
"customfield_10110":{
"name":"{{Developer}}"
},
"priority":{
"name":"{{Priority}}"
},
"customfield_10125": "{{Class}}",
"customfield_10126": "{{Module}}",
"customfield_10127": "{{MainComponent}}"
}
}
You can use POST /rest/api/3/issue/{issueIdOrKey}/transitions
You can transition an issue to the Create DEAP option, but you will need to know the transition ID. (which you can get from /rest/api/3/issue/{issueIdOrKey}/transitions)
There is also the option to fill any screens that appear on the workflow transition.
See the Transition issue part of the documentation for further details- https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-transitions-post
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Danh,
This could be a number of things:
- Are the values you are putting into your fields valid? I.e. Is the reporter value a real user in jira with access to the project? Are any of the customfields select fields and you are not using a valid value? Does the issuetype you are using exist? ...etc
- Are there any required fields that you have not specified a value for?
- Are there any conditions / validators on the project workflow that have not been met? Or any post functions which may be causing issues.
Do you have access to the jira logs to see if it provides more information?
I would first try to create the issue in jira using the exact values your API POST is using and see if that works or you get the same problem.
Regards
Evan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you referring to DEAP been created as an issue type through the API or something else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create the DEAP issue type via the API.
using POST /rest/api/2/issuetype
{ "name": "DEAP", "description": "description", "type": "standard" }
See documentation for more details
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry not sure I understand? Do you want a DEAP project via API?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The DEAP project is already created. I just need to create Jira with DEAP type by API (GUI is created successfully). Look like we are not supporting this scenario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you provide a screenshot from the GUI of what you mean by DEAP type? I can then hopefully be able to assist you further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
{ "errorMessages": ["We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file."], "errors": {} }
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.