Update plan using REST API

[Cláudia Sardinha]

I want to create cross-project releases using Jira REST API.

I've tried a PUT and a PATCH request to rest/api/3/plans/plan/{planId} and I got 415 and 400 responses.

I've tried the following payloads:

PUT
{
  "releases"/"crossProjectReleases": [{
      "name": "2.99.0"
    }]
}

PATCH

[

  {

    "op": "add",

     "path": "/releases/-" OR "/crossProjectReleases/-",

     "value": {

          "name": "2.99.0"

     }

  }

]

I've tried Accept: application/json and Accept: application/json-patch+json.
Nothing works.

I'm able to perform different requests to different endpoints without any problem.
Can you point me on the right direction please?

Thanks

[Philipp Sendek _catworkx_]

Hi @Cláudia Sardinha and welcome to the community!

I've spent some time trying to figure it out, but I end up in the same issue you do: Mostly 415. Also there's no documentation on how to properly map the JSON Patch scheme to the fields. Maybe someone will pick up this question who has the answer.

Until then I can share that I've made good experience with using the internal REST endpoints that the browser uses in the background when you apply changes to the plan through the UI.

In case you're not familiar with how to do this:

- Open the Network Tab in the Developer Tools of your browser. Load the configuration page where you'd manually would the adjustment that you want to automate. Wait for the page to load. and then clear the network tabs contents.

- Now perform the action and look for the "update" request in the network tab:

- Click on this request and copy the URL and the Payload. By adjusting the payload and using this internal REST endpoint, you should be able to automate what you're looking for.

Those internal endpoints should always be used with caution, but for this particular one I can tell you that I've built production automations for clients years ago and they still run to this day. So it doesn't seem to be changed; and if so, Atlassian hopefully versions them properly, so that using version 3 will grant you a stable endpoint.

I hope this helps!

Greetings
Philipp

[Cláudia Sardinha]

Hi @Philipp Sendek _catworkx_,

Yap, it works like a charm.

Thanks for sharing!

[Ken NAKAMATSU]

I updated the Planlead and permissions via the web API.

The request body used the PATCH format like this:

[ 
  {"op":"replace", "path":"/leadAccountId", "value": "xxx"}
]

The method was PUT, and the header included Accept: application/json-patch+json.

From your example, it seems the value might not be correctly specified.
Based on the output from a GET method,
it looks like the releaseIds is required.
Here's an example of how it should look:

[
  {
    "op": "add",
    "path": "/crossProjectReleases/-",
    "value": {
      "name": "x-plr",
      "releaseIds": [345]
    }
  }
]