Hi @Antonino_La2 ,
We are running On-Prem instance of Chronicle SOAR v6.2.7.7 and Jira integration is working fine for both our internal and SaaS instances of Jira.

hi, im also not familiar with any issues with this integration, please make sure you are using the latest official marketplace version of integraiton

Hi @Louis_Mesmin did you make any other configuration then create API token in jira instance? I think I'm missing something in my configuration..

Hi @Dmitry_Sarakeev I've downloaded the integration directly from the marketplace and it's the latest version

strange, does other actions work?

maybe you are trying to create a non existing type of ticket, i now remember that i have something similar, when i tried to create a ticket type that does not exist in Jira

Mhhh now I'll try other actions. For this one I'm trying to open an issue with a custom issue type defined in my project.

yeah it may be the issue type, try to open with the most basic one type: Task

With Task issue type I get "Failed to create issue in project BIP. Error is Issue type Task was not found.". So I suppose that the problem is not that

ok, please check the ticket types in your jira

Tryied with another issue type defined in my project "Generic Request" but I get again the HTTPError

I searched through the integration code for objects that are calling a 'text' attribute and found the ones in the attachment.

View files in slack

Dear @Antonino_La2 , I remember that we struggled a bit on the Jira side at start to correctly configure the type of issue, the skeleton of each issues and to adapt our action configuration in playbooks to match this.
As a reference I used Firefox and tried to acces an example of an issue manually created to better understand the mapping and the values.
With Firefox using https://YourJiraFQDN/rest/api/2/issue/OneOfYOurTicket

For example, as we are a French company, part of the visible values in Jira WebUI is translated in French but real values to use from the API is the english equivalent most of the time.

It comes out that if I left the field "Assignee" blank it works.. I'll troubleshoot that now, thanks everyone!

Ah ! Assignee is a tricky field.
We had issues in the past with it and we are still using a custom action for assigning the issue in Jira but Chronicle Support should have fixed the issues we experienced specially with GDPR mode on our Jira SaaS instance.