What is the bug?

If I define a custom field id of type number, the table couldn't render.

How can one reproduce the bug?

Define a field of type number and define these field as custom field id.

What is the expected behavior?

The table should render correctly with this values of this custom field.

What is your host/environment?

OS: Ubuntu 22.04 LTS
Node: v16.x

Do you have any screenshots?

no

Do you have any additional context?

no

Is your feature request related to a problem?

If a JIRA JQL is wrong or misspelled the error is not clear, to the user.

What solution would you like?

The extension should log the problematic JQL and stop continue processing.

What alternatives have you considered?

no alternatives exists.

Do you have any additional context?

no

Is your feature request related to a problem?

SSO is active in our Jira. When I try to embed Jira issues via the block macro, nothing is displayed. I have seen that Basic Auth is used in the Jira.js file. I have tried the following combination

JIRA_USERNAME: username / JIRA_APITOKEN: password
JIRA_USERNAME: username / JIRA_APITOKEN: personal access token
JIRA_USERNAME: email / JIRA_APITOKEN: password
JIRA_USERNAME: email / JIRA_APITOKEN: personal access token

I always get a 401 error from Jira.

What solution would you like?

Is it possible that the personal access token can also be transferred as a bearer token as authentication as alternative to username:password?

lib/Jira.js constructor

if (jiraUserName )        
  const auth = 'Basic ' + Buffer.from(jiraUserName + ':' + jiraApiToken).toString('base64')
else if (jiraPersonalAccessToken)
  const auth = 'Bearer + jiraPersonalAccessToken
    
this.headers = {
  authorization: auth
}

What alternatives have you considered?

Do you have any additional context?

Is your feature request related to a problem?

Some fields from Jira may be returned as array (e.g. custom fields) - this is not covered by plugin and data are not shown.

What solution would you like?

To add conversion of data from array before trying to convert data from object (file asciidoctor-jira.js, after line 50), such as:

if ( value != null && (value.constructor === Array) ) {
              value = value.toString()
            }

What alternatives have you considered?

There are no alternatives if you want to be able to view the jira fields that are returned as array.

Do you have any additional context?

I've tested the modification and it works. I apologise for not creating a pull request as I do not primary operate on a public github.

It should be possible to use a nested issue key e.g. reporter.displayName, it would be nice if we can use default and label values for this nested properties as well.

What is the bug?

Issue type icon is always rendered as image in front of issue key column.

How can one reproduce the bug?

Define customFieldIds without issuetype as column name.

What is the expected behavior?

Issue type icon should only rendered, if issue type is defined as custom field id.

What is your host/environment?

OS: Ubuntu 22.04 LTS
Node: 16.x

Do you have any screenshots?

no.

Do you have any additional context?

no.

It would be nice if the issue id column size is 1 and all other columns has the column size of 2.