I am creating bulk issues using issue/bulk and I need to set the specific workflow of the created issues
How can i change the transition of issue while creating it
Hi @Saurabh Bhandari ,
You cannot. It will first need to be saved in the initial state and then transitioned in a different call to the correct State.
You will need the id of the issue that was created to transition it so it has to be 2 calls.
A workaround could be to add a custom field with a flag or something and then set an automation in JIRA to auto transition the issues to this state based on that "flag"
Hello @Saurabh Bhandari ,
You can use the CSV method to create the bulk issues and while importing the issues you can change the status of the issues but this wouldn't be called as transitioning of the issue, like we can map the status of the issue through the UI.
But I am not sure when you say - need to set the specific workflow?
But for performing the transition using API, it would require the issue id, to perform the operation, where in we can get the issue id, post the creation of the issue.
So we might have to create the issue, retrieve the issue id for those and then perform the transition.
Thanks and Regards,
Ganesh Babu J
Instead of a flag you could also set the State that you want it to go to in a custom field and then based on that transition to the correct state (after creation of course)
Thanks for the reply It was helpful.
One more question :
In which case I will get the value of status field under transition node on create issue response
{ "id": "10000", "key": "ED-24", "self": "https://your-domain.atlassian.net/rest/api/3/issue/10000", "transition": { "status": 200, "errorCollection": { "errorMessages": [], "errors": {} } }}
What does it indicate and what fields I need to add on request
Hello @Saurabh Bhandari
To get the value of the status, you need to execute the Get transitions api call which is going to provide you the value for the status field. Or It is using the workflow statuses api,
The transition is going to be performed based on the transition id.
Important is that the endpoints for transition & creation are different
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#status-codes
@Saurabh Bhandari ,
Details regarding the transition itself you can find here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-transitions-post
The id of the transition (cause you perform a transition from status A to status you will need to find in your instance (this is specific to your environment)
From what I can see both the transition and the creation use the same endpoint so the response might only contains something in the transition when it was done.
It looks like you're new here. Sign in or register to get started.
