Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Webpanel not showing content in Issue View from Queue

dberrutti
Contributor
April 22, 2024

Hello community,

I'm having a hard time with a webpanel which shows in Issue view, here's the context:

The webpanel is defined like this:

<web-panel name="panel name"  key="issue-view-panel" location="atl.jira.view.issue.right.context">
.....
<resource name="view" type="velocity" location="templates_path/template.vm"/>
<context-provider class="fullyqualifiedclass"/>
</web-panel>

Which uses resources (css and javascript generated via webpack) defined like this:

<web-resource key="entrypoint-main">
<transformation extension="js">
<transformer key="jsI18n"/>
</transformation>
<context>atl.general</context>
<context>customerportal</context>
<context>servicedesk.general</context>
<context>jira.general</context>
<dependency>com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path</dependency>
<resource type="download" name="myplugin-main-min.css" location="frontend/myplugin-main-min.css"/>
<resource type="download" name="main.js" location="frontend/main.js"/>
</web-resource>

And the template loads the resource (and sets the element to load React page) like this:

 

$webResourceManager.requireResource("my.plugin.path:entrypoint-main")
<div class="ac-content">
<section name="sourcePage" id="some_id">
</section>
</div>

 

In the issue view from "browse" (http://localhost:2990/jira/browse/ISSUE_KEY) the content is correctly loaded, showing the page created in React.

However, in the issue view from "queues" (http://localhost:2990/jira/projects/<PROJECT_KEY>/queues/custom/1/<ISSUE_KEY>) it shows the panel link, but no content, or better saying, loads the HTML that is in the velocity template, but does not load anything from the React page.

Does anyone have an idea of what might be missing here?

 

 

 

1 answer

1 accepted

1 vote
Answer accepted
dberrutti
Contributor
April 23, 2024

I found the problem, nothing to do with the location, just when the page was loaded, the section 

id="some_id"

was still not available. Added some typescript to wait for it to be available and it worked.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events