How can I initialize a Jira project with the REST API?

Other Questions Jira
1 
{
  "project_code": "TESTPROJ",
  "project_name": "Test Initiative",
  "project_category": "operations",
  "template_id": "jira-ops-simplified-template",
  "project_description": "Demo project created via REST call",
  "ownerIdentifier": "",
  "projectLink": "",
  "roleAssignment": "PROJECT_OWNER",
  "iconReference": 1305
}

I attempted to create a project using Python and verified it with a REST client, but I received a 404 error. I need clarification on what information to supply for the empty fields ‘ownerIdentifier’ and ‘projectLink’, and which attributes are required in the JSON payload for creating either a project or an issue.

2

Based on personal experience, a 404 error in Jira’s REST API can be due to either an endpoint mismatch or an incomplete payload. The ownerIdentifier field should not be left empty; it must contain a valid account ID of the person responsible for the project. The projectLink, if not mandatory for your instance, generally needs to be a proper URL if used. Ensuring that all required fields are correctly filled, in accordance with your particular Jira setup, is essential. Reviewing the documentation for your Jira version can lead to a successful setup.

3

i had a similar issue. make sure you use a valid acount id for owneridentifier; leaving it blank may cause a 404. if projectlink isnt required, try omitting it. also, double-check that your api endpint is correct for your jira version.

4

In my experience, the root cause of a 404 error when initializing a project through Jira’s REST API often lies in using an inappropriate endpoint or sending an incomplete payload. I encountered a similar issue and found that both the ownerIdentifier and projectLink fields need careful handling. For ownerIdentifier, you really must supply a valid account ID according to your Jira instance requirements. As for projectLink, if it’s not in use, either omit it or follow the format specified by your version of the API. Verifying against your API documentation helped me resolve these issues.