The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
- Community
- Q&A
- Confluence
- Questions
- Some gadgets (BigPicture Gantt) are not working as expected with Jira (HTTP 403)
Some gadgets (BigPicture Gantt) are not working as expected with Jira (HTTP 403)
Hi all,
we observed quite a strange behaviour with our BigPicture Gantt gadgets, that we regulary use in Confluence and Jira.
When using those in Jira dashboards, the initial view is identical. We can then use quick filters that are predefined in the BigPicture box to reduce the number of issues. This is working flawlessly.
However, using the same gadget in Confluence and referring the same box as in the Jira dashboard, the initial view of the entire box is working fine, but we are unable to use the quick filters.
I have seen in the browser console, that there are some errors shown.
The following URL request appears to be related to the incorrect behaviour:
I am getting this error as a response:
<!doctype html>
<html lang="de">
<head>
<title>HTTP Status 403 – Forbidden</title>
<style type="text/css">
body {
font-family: Tahoma,Arial,sans-serif;
}
h1, h2, h3, b {
color: white;
background-color: #525D76;
}
h1 {
font-size: 22px;
}
h2 {
font-size: 16px;
}
h3 {
font-size: 14px;
}
p {
font-size: 12px;
}
a {
color: black;
}
.line {
height: 1px;
background-color: #525D76;
border: none;
}
</style>
</head>
<body>
<h1>HTTP Status 403 – Forbidden</h1>
<hr class="line"/>
<p>
<b>Type</b>
Status Report
</p>
<p>
<b>Message</b>
XSRF check failed
</p>
<p>
<b>Beschreibung</b>
Der Server hat die Anfrage verstanden, verbietet aber eine Autorisierung.</p>
<hr class="line"/>
<h3>Apache Tomcat/9.0.65</h3>
</body>
</html>
The description is in German, and means something like: The server understood the request, but does not allow the authorization.
As the plugin is working fine initially, I do not understand why this happens out of a sudden.
Did you ever experience this kind of behaviour?
Thanks for your help!
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.