Automated creation of jira issue fails

[Vikas Mahajan]

I am using this https://<domain>/rest/api/2/issue endpoint to automate creation of some scheduled tasks which was working fine for months now but all of a sudden i can see this automation failing with all the error statements indicating 

The mentioned projectId <projectID> for project name <project-name> is invalid. Specify a valid projectId

The reporter <email-id> doesn't seem to be part of project. Specify a valid reporter mail Id

I have verified manually by creating an issue from console and the reporter and task assignee are valid. Project ID is also correct which I have verified from this below api

https://<your-domain>.atlassian.net/rest/api/3/project

I am using python 3.9 running on lambda with requests library to make these requests. 

I tried creating new api token and tested with that as well but that didn't help.

So, not sure the reason why the automation fails all of a sudden now. Any help or insights would be appreciated.

Thankyou

[Marc -Devoteam-]

Hi @Vikas Mahajan 

This request is a duplicate of your earlier post, https://community.atlassian.com/forums/Jira-Service-Management/Creation-of-issue-fails/qaq-p/3213641 

[Ajay _view26_]

Hi @Vikas Mahajan 

A few things in your error message point more to field validation / permissions than to a Jira outage.

The two biggest things I would check are:

1. Reporter format
In Jira Cloud, user fields should generally be sent as account IDs, not email addresses. If your payload is still setting reporter/assignee by email, that is a likely cause.

2. Create metadata / permissions
The Create Issue API only accepts fields that are valid on that project + issue type create screen. Atlassian recommends checking the create field metadata for the specific project and issue type, because those allowed fields can change over time.

So my first guess is not that the project ID suddenly became invalid, but that Jira is now rejecting one or more submitted fields for this create context.