The CLI never surfaces the numeric Jira issue id (the REST id field). jira issue view KEY --format json returns only {fields, key}, and jira search --columns id renders an empty column.
Use case: building integrations that need the numeric id — e.g. attaching a Jira issue as Timely 'linked work', whose payload requires the numeric external_id (the issue key alone is not resolved by Timely). There is currently no way to obtain it from the CLI.
Request: include the numeric id in issue view JSON output, and make id selectable via --columns id in search / issue list.
The CLI never surfaces the numeric Jira issue id (the REST
idfield).jira issue view KEY --format jsonreturns only{fields, key}, andjira search --columns idrenders an empty column.Use case: building integrations that need the numeric id — e.g. attaching a Jira issue as Timely 'linked work', whose payload requires the numeric
external_id(the issue key alone is not resolved by Timely). There is currently no way to obtain it from the CLI.Request: include the numeric
idinissue viewJSON output, and makeidselectable via--columns idinsearch/issue list.