[Security Solution] [Bug] User is unable to select the 'Issue type' for the Jira connector while adding it to cases

[muskangulati-qasource]

Describe the bug User is unable to select the 'Issue type' for the Jira connector while adding it to cases

Kibana/Elasticsearch Stack version

VERSION: 8.16.0
BUILD: 78245
COMMIT: b5dcc0db8dc72e25fcda6894ed6f24b6959b15b3

Steps

1. Add a connector for Jira
2. Create a case
3. Add jira to the connector
4. Observe the user is not able to add the 'issue type' and hence the connector can not be added to the case

Expected Result

• User should be able to select the 'Issue type' for the Jira connector while adding it to cases

Screen Recording

https://github.com/user-attachments/assets/c33f59a7-fe7d-439f-bcc0-471cffa71aea

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[amolnater-qasource]

Reviewed and assigned to @vgomez-el & @pborgonovi

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[cnasikas]

It seems that Jira does not return the issue types when requesting them. Either no issue types are configured properly or the user does not have access to the issue types. I cannot reproduce it with my configuration. Do you see any error log in Dev Tools (Console or Network tab)?

[vgomez-el]

@muskangulati-qasource can you check what @cnasikas is saying, please? Thank you

It seems that Jira does not return the issue types when requesting them. Either no issue types are configured properly or the user does not have access to the issue types. I cannot reproduce it with my configuration. Do you see any error log in Dev Tools (Console or Network tab)?

[muskangulati-qasource]

Hi @cnasikas & @vgomez-el,

Please find below the observation from the Network logs:

https://github.com/user-attachments/assets/e478926b-25e3-4008-860f-cfa9ea884503

There are no error logs generated for the same.

Please let us know if anything else is required from our end.

Thank you!!

[cnasikas]

@muskangulati-qasource Could you please check the response of the _execute HTTP call in the Network tab?

[muskangulati-qasource]

Hi @cnasikas,

Please below attached video and file for the _execute response

Screen Recording

https://github.com/user-attachments/assets/00ffe0bf-8491-45ef-8962-2c6017c218bb

Text file testData.txt

Please let us know if anything else is required from our end.

Thank you!

[cnasikas]

@muskangulati-qasource It seems that Jira returns no issue types for the current user the connector configured with. It seems like a Jira configuration or permission issue and is not related to Kibana. Thanks!

[muskangulati-qasource]

Hi @cnasikas,

Thank you for the update. Do you want us to close out this ticket?

[cnasikas]

I would say yes as we cannot reproduce it with our configuration. Could verify that this is the case though?

[muskangulati-qasource]

@cnasikas,

Thank you for looking into the issue, if it needs to be tested with different configuration, can you share the API key and the project ID being used with the credential information?

We can check once and will share the observation!

Thanks!

[cnasikas]

As I have already tested my configuration and can verify that it is working, I suggest going to Jira and verifying that your configuration is different. Wdyt?

[muskangulati-qasource]

Hi @cnasikas,

Please find below the details of the issue types being generated under Jira:

Please let us know if anything is missing from our end.

Thank you!

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[cnasikas]

@muskangulati-qasource Do you use the same project for the connector (Qa_Testing)? Jira allows complicated configurations. Because you see the type in the UI it does not mean the API will return it.