nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AJAX based project, component, version fields

Dmitry Nechayev

It looks like project, component and version autocomplete fields do not use AJAX and load the whole set of values into browser memory. This makes all aforementioned fields not really scalable. I had delays up to 20 seconds upon opening CreateIssue dialog in configurations with several thousands (up to 4) of projects or components and versions

Is there any recommended way to go around this behavior and avoid pre-loading all project, component, and version values?

Thanks!

Accepted answers

Jobin Kuruvilla [Adaptavist]

It is not configurable but you should be able to modify the related velocity templates and load them as you want. For example, loading projects is controlled using atlassian-jira/WEB-INF/classes/templates/jira/issue/field/project-edit.vm.

All comments

Jobin Kuruvilla [Adaptavist]

Dmitry Nechayev

Thank you! As I understand, I can modify vm templates to make these fields as text edit fields (without loading all values in a list) but it is unlikely that I can make them AJAX based without changing Jira classes...

Jobin Kuruvilla [Adaptavist]

Well, you should be able to make it Ajax based too by using the existing REST services

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

performance

auto-complete

scale

ajax