nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

API Jira issue update

Māris Lazda

Have been using jira api for years to automatically assign developer to an issue.

Nothing has been changed but from today if I try to update jira issue I just get a response code 204 and nothing changes (assignee field still empty)

PUT request: https://***.atlassian.net/rest/api/2/issue/MD-23468

body:

{"fields":{"assignee":{"name":"***"},"customfield_11517":[{"name":"***"}]}}

Is there an issue with jira api right now? I got no other explanation

Accepted answers

Board Genius

I started having this problem when trying to create a project and specifying the project lead by username. I now have to specify leadAccountId and use accountId.

This deprecation is explained in the API docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-project-post

There is also general info here on deprecations across the API:

https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

All comments

Fernando Giovanini

We use Jira REST to search for issues and today it started failing.

We are using it with Jenkins (Jira Step plugin). Are you using the API with Jenkins?

dhollinger

I ran into this the other day using https://github.com/andygrunwald/go-jira. It appears that name is not longer returned by the Jira API. I had to use displayName.

Additionally, I'm seeing this on API requests as well: Invalid Usage: 'accountId' must be the only user identifying query parameter in GDPR strict mode.

It appears to be related to a deprecation from the last couple years: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

Board Genius

I started having this problem when trying to create a project and specifying the project lead by username. I now have to specify leadAccountId and use accountId.

This deprecation is explained in the API docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-project-post

There is also general info here on deprecations across the API:

https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

Mauricio Jovel

I did this PR to try to fix this @dhollinger https://github.com/jenkinsci/jira-steps-plugin/pull/103 waiting for the approval

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud