Jira init fails at configuring metadata step

[adezxc]

jira init fails when running /rest/api/2/issue/createmeta endpoint. I am not sure if it's my work instance's specifics, but I get a 404 at that step after choosing a board (even if I choose None). I think this is related due to the createmeta endpoint getting deprecated (https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-1304) If you could confirm this, I'd be happy to try and undertake the task of migrating to /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes and /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

Please provide following details

1. JiraCLI Version:

   (Version="v1.5.1", GitCommit="", CommitDate="", GoVersion="go1.22.3", Compiler="gc", Platform="linux/amd64")
   

2. Are you using Jira cloud or on-premise jira server?
   Jira cloud enterprise instance
3. What operating system are you using? Also mention version.

   Debian Linux on WSL2
   

Output when running jira init --debug --installation cloud --server https://jira-instance.com --login [email protected] --project DMGTM --board 'None' --auth-type bearer

GET /rest/api/2/myself HTTP/1.1
Host: jira-instance.com
Authorization: Bearer <token>

⠹ Fetching projects...

REQUEST DETAILS
------------------------------------------------------------

GET /rest/api/2/project?expand=lead HTTP/1.1
Host: jira-instance.com
Authorization: Bearer <token>

⠧ Fetching boards for project 'DMGTM'...

REQUEST DETAILS
------------------------------------------------------------

GET /rest/agile/1.0/board?projectKeyOrId=DMGTM HTTP/1.1
Host: jira-instance.com
Authorization: Bearer <token>

⠙ Configuring metadata. Please wait...

REQUEST DETAILS
------------------------------------------------------------

GET /rest/api/2/issue/createmeta?projectKeys=DMGTM&expand=projects.issuetypes.fields HTTP/1.1
Host: jira-instance.com
Authorization: Bearer <token>

✗ Received unexpected response '404 ' from jira. Please try again.

[ankitpokhrel]

Related #742 #726

This was fixed with #447 🤔.

Are you sure you are on a cloud instance?

[quentincaffeino]

I experience the same behavior with
Go: 1.23.0
Jira cloud: v9.4.23
Jira cli: 1.5.1