Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,630
Community Members
 
Community Events
176
Community Groups

All .js & .css (.vm) rendered twice on search issue page

We have a Jira server app named "UpRaise for Employee Success".
In this app, we have added a web-panel on Jira issue details page.
We have noticed our page is rendered twice on the "search" issue page.
So, all js and CSS are loaded twice, as well as initial calls made from react to fetch data to show in our web panel, are fired twice.
Steps to reproduce this issue,
1. Go to "Issues -> Search for issues" and click on any issue in the search result on left-hand panel
2. Check network response all js and CSS are rendered once e.g vendors~app.8339f357.chunk.css
3. Then click on other issue & again click on the first issue then observer vendors~app.8339f357.chunk.css rendered twice
Please note that this issue is not reproducible from the issue details page. The problem is only with the search issue page.
Please see attached screenshot & issue.har file for more info.

1 answer

Have you found a workaround? I am facing the same error, and specifically in search issue page as you mention.

It has been reported as a bug before (JRASERVER-42752) , and there seems to be no definite/agreed solution for it.

PS: It seems your attachments have not been uploaded.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events