We noticed this issue happening as well on Feb 2, 2023. As soon as I noticed it, we quickly fixed the issue on the Issue Linking page. At the time, we assumed that someone on our team accidentally reversed the labels or a bug with Atlassian. On Feb 17, 2023, I noticed that the Blocks type got reversed again. That made me realize that it couldn't be anyone of the team since nothing was showing up in the Audit Logs. I decided to open a support ticket with Atlassian, asking them to help identify who or what was causing the issue.
Atlassian replied back to inform me that an API call made by BigPicture was causing this issue. This is what showed up in the logs on Feb 13, 2023 (reformatted for improved readability).
{
"eventName": "jira.public.rest.api.call",
"resourceName": "IssueLinkTypeResource",
"resourceMethodName": "updateIssueLinkType",
"httpMethodName": "PUT",
"httpResponseCode":200,
"path": "/api/{v:2|3|latest}/issueLinkType/{issueLinkTypeId}",
"pathPrefix": "",
"fullPath": "/api/3/issueLinkType/{issueLinkTypeId}",
"connectAddon": true,
"connectAddonKey": *"eu.softwareplant.bigpicture",*
"userAgent": "Java/11.0.17",
"clientType": "CONNECT_SERVER_TO_SERVER",
"executionTimeMillis": 86,
"data": {},
"exceptionClassname": null
}
After being provided that useful bit of information, that's when I discovered this thread, as well as 2251345.
Appfire really needs to fix this ASAP; otherwise when we link our issues, everything is going to be linked backwards moving forward and it going to cause confusion later down the road once the issue has been resolved. I guess in the interim, I'll have to check the Issue Linking daily and fix it manually until Appfire resolves the issue.
Does anyone know if it's possible to downgrade to 8.10.1?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.