Status of OJSI tickets that should be fixed for Frankfurt

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

General status of all OJSI tickets

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Status of OJSI Tickets with CVE assigned

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Status of OJSI Tickets related to HTTP exposed outside of a cluster

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

List of tasks related to ports which has not been detected as HTTP ports during recent scan:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Status of OJSI Tickets with fix version = Dubliin, El Alto, Frankfurt

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Key Summary T Created Updated Due Assignee Reporter P Status Resolution Fix Version/s
Refresh

  • No labels