Bulk edit issues fix Version via rest

Jira Development
1

I can create and edit fix versions, and apply issues to them one at a time via the rest API, but I cannot seem to make the BULK edit issues endpoint work via rest in order to apply a list of issues to a fix version

It seems as if a few years ago there were discussions saying this wasn’t possible, but more recently there are posts linking to this page:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-fields-post

Which claim the api has this functionality, it seems as if it should be possible??

I can interact with the endpoint via a post request and have tried many json req bodies, but the closest I can get to success is an error message saying “no issue data was provided by request”

I am hitting the endpoint rest/api/latest/issue/bulk, and I am using an api key which works for many other functions throughout the api

I essentially want to {update: fixVersions: add: id: “versionID”} for a list of issueKeys

2

This announcement seems to claim exactly what I want to be able to do!

Is it possible that this only works on jira cloud, whereas my company’s jira server would for some reason not qualify?

3

Yes, the endpoint is only available in the v3 REST API of Jira Cloud, but that doesn’t explain how you are able to ‘interact’ with that endpoint if you have Jira Server or Data Center.

What is the path / URL to your Jira instance?

That little piece of information will immediately let me know if you are on Cloud or Server / DC and therefore why that endpoint is causing a problem.

4

If I attempt to follow the documentation that links from the bulk api announcement, which seems cloud specific, ie:

Jira.mycompany.tools/rest/api/latest/bulk/issues/fields?issueIdsOrKeys=ISSUE-1234

I get a 404, and I have tried some variation in that path

But after some trial and error, If I send a get request to

Jira.mycompany.tools/rest/api/latest/issue/bulk

I instead get a 405, method not allowed. Which made me think maybe I had figured it out, so I instead post request to that same uri and no matter what I seem to do there, I am getting an 400, error message “no issue data was provided by request”

I have attempted to structure my json according to the cloud api docs, and also with any other json keys I could think of that might work to define the issue data,

So is what I am trying to do possible, and I am just doing it wrong? I just want to add a fix version to a list of issues, it seems so simple in theory

5

There is no such domain ‘Jira.mycompany.tools’. It’s a fake / placeholder domain.

What is YOUR company’s Jira domain? What is the path you use to login to your company’s Jira instance?

6

Correct, my client is not actually named “mycompany” that’s just a placeholder, would these not be essentially universal within the jira ecosystem? I would think that the important pieces of the path would come after rest/api

I can utilize other endpoints, getting/posting issues/ versions etc, and adding any individual issue to a fix version at a time, I am just apparently misunderstanding how to operate the bulk functionality of the api.

7

I have asked you TWICE to provide specific information to be able to help you, but you won’t provide it.

would these not be essentially universal within the jira ecosystem

Nope.

I have no further assistance to offer to you. I suggest you try the Jira section of the public Atlassian forum.

Good luck.

8

Haha, in what way is the actual name of the company utilizing the software critical? Please pardon my ignorance, but I am fairly certain that nowhere else in any of these threads has that been the determining factor

9

Also, you catch more flies with honey, :honey_pot:

10

………. My endpoint is jira.sunnyape.tools/rest/api

It’s just a weird coincidence and I didn’t want to bring it up. We are on a server instance, not cloud. :person_shrugging: