from jira import JIRA
client = JIRA(basic_auth=(username, password), options={'server': base_url})
query_string = 'project=STORM AND status in (Open, "In Progress", "Ready for Review") AND Component="Analytics" AND issue in tts.issuesHaveSomeExceededSlas("Critical Security Risk", "High Security Risk", "Medium Security Risk", "Low Security Risk") ORDER BY "Security Risk" DESC, created ASC'
issues = client.connection.search_issues(query_string)
Got this error
JIRAError: JiraError HTTP 400 url: https://jira.inside-zen.com/rest/api/2/search?jql=project=STORM+AND+status+in+(Open,+"In+Progress",+"Ready+for+Review")+AND+Component="Analytics"+AND+issue+in+tts.issuesHaveSomeExceededSlas("Critical+Security+Risk",+"High+Security+Risk",+"Medium+Security+Risk",+"Low+Security+Risk")+ORDER+BY+"Security+Risk"+DESC,+created+ASC&startAt=0&validateQuery=True&fields=*all&maxResults=50
text: Unable to find JQL function 'tts.issuesHaveSomeExceededSlas(Critical Security Risk, High Security Risk, Medium Security Risk, Low Security Risk)'.
response headers = {'Date': 'Sat, 18 Mar 2023 07:57:22 GMT', 'X-AREQUESTID': '57x13797315x1', 'X-ASESSIONID': 'j021tz', 'Referrer-Policy': 'strict-origin-when-cross-origin', 'X-XSS-Protection': '1; mode=block', 'X-Content-Type-Options': 'nosniff', 'X-Frame-Options': 'SAMEORIGIN', 'Content-Security-Policy': 'sandbox', 'Strict-Transport-Security': 'max-age=31536000', 'X-Seraph-LoginReason': 'OK', 'X-AUSERNAME': 'prodsec-service', 'Cache-Control': 'no-cache, no-store, no-transform', 'Content-Type': 'application/json;charset=UTF-8', 'Access-Control-Allow-Origin': 'http://localhost:8000', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Content-Length': '150', 'Connection': 'close'}
response text = {"errorMessages":["Unable to find JQL function 'tts.issuesHaveSomeExceededSlas(Critical Security Risk, High Security Risk, Medium Security Risk, Low Security Risk)'."],"errors":{}}It was working just fine until 2023/02/20. The weekly task has been failing since 2023/02/27
I am using jira 2.0.0 and tried using latest version (3.5.0) but it didn't fix the issue.
