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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Include web resources conditionally with CDN feature support (Jira 8.3 compatibility)


After Jira DC (8.3) compatibility with CDN announcement we have faced the problem with one of our conditionally included resources that we have to convert to stateless conditioning.

There is a resource (Javascript + CSS) with a significant size (couple of MB) and significant initialization time that should be included into jira.view.issue context (page body) depending on user settings. There are couple of ways to make it CDN compatible (stateless):

  • just remove stateful condition - users who should not load the resource will have page load extra time overhead.
  • move scripts to web-panel - bad idea in any case. Script will load and initialize on any issue change in issue navigator.
  • use stateless condition - will require to include user key/id into resource URL that seem also bad. CDN will have a huge set of identical resources for each user.
  • include resource and its dependencies by small bootstrap script inserting resources tags into body - will also affect page load and probably CDN effectiveness because such resources will not bundled into batch

So is there any legal and performance efficient way to make such conditional resource include?


Alexey Stepanov | ALM Works Structure development team

1 comment

Seems this should be posted to dev community :)

Any way the solution is to calculate condition on resource URL build time and put result into URL params. The only thing you will not be able to deel with such approach is security - URL params can be modified by somebody and resource can be disclosed.


Log in or Sign up to comment