The add-on uses some deprecated Jira endpoints, and some of them, such as “/search,” are already removed by Atlassian and will no longer be operational. Here are the endpoints and their alternatives: GET /rest/api/latest/search -> GET /rest/api/latest/search/jql You only need to modify the URL; no parameters change between the two endpoints. However, we see that these endpoints are only used to obtain a count of issues, so we recommend using this other endpoint: POST /rest/api/latest/search/approximate-count GET /rest/api/latest/project -> GET /rest/api/latest/project/search Changes the URL, now you need to paginate and the format of the response changes. Now the expected results are received within “values”: GET /rest/api/latest/resolution -> There is still no alternative available that is not in experimental mode. GET /rest/api/latest/priority -> There is still no alternative available that is not in experimental mode. ... View more

Hi, Firstly, thank you for the work on this addon and thanks the community that is solving problems helping each other. We have a Splunk Cloud that we want to connect with Jira using this addon. The idea we have is to send to Jira all the tickets that will create Splunk and manage them in Jira. When the ticket is closed in Jira, we want to update all the information, comments and updates in the ticket to visualize them in Splunk. Any ideas or URL that would help us configuring this function? Maybe with webhook? Thank you so much, Kindest regards. P.S: Sorry about my english, it is not the best 🙂 ... View more