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; } } }

Advanced Roadmaps resoure usage of improved interface

unknown

We have a Jira environment for 2000 users on Jira server v8.9.1 testing Advanced Roadmaps. We have a test environment with just a few projects and almost none issues. When we set-up a plan that consists of 2 other plans in total about 12 teams.

If we are using the new improved interface the response time of the system is between 45 seconds and 1 minute to just load the plan overview. Selecting filters will also take another 45 seconds or more and any selection box will take another 30 to 45 seconds.

However, the moment we switch off the improved interface we have excellent response times with the same actions.

Can we control this in any way?

Comments

Dave

Hi Hans,

Thanks for raising this question - this sounds like an unusual situation and if you have paid support (i.e. you're not on a free trial) then I'd recommend reaching out to your support representative to get some assistance here.

However, there are a few things about your question that would be useful to clarify...

You've said that you've created a plan that consists of 2 other plans? Do you mean that you've created a plan that has the same issue sources as 2 other plans? As it's not possible to create plans from other plans? Unless you meant a program?

The other thing that I didn't quite follow is that you've said that when you switch filters it takes 45 seconds or more... however, filtering in the new interface is done entirely in the frontend code and the performance should only be impacted by the number of issues loaded into the plan - yet you've said there are almost no issues?

It would be really good if you could clarify how many issues are being loaded into the plan and how many issue sources you have (e.g. projects, boards and/or JQL filters).

We do know that certain things can reduce plan loading times (complexity of JQL filters used for issue sources, the number of releases in the project, etc) but these should have the same impact on both the old and new interface.

We're obviously concerned about these performance issues you're encountering and would like to understand them better and resolve them for you!

Regards,

Dave

unknown

Hi Dave, we have dropped issue with our vendor Prepend so the formal way is also followed.

I will create a copy of the plan that we have problems with.

Create plan named Bigtoom test plan
Select issue sources (31 boards)
Select some release
Add teams (boards)
Add two boards where we created plans for already
Done

After comparing the two plans I discovered that in the problematic plan one issue source is doubled. The newly created copy of the first seems to have good response.

After deleting the doubled issue source the response time is ok now.

Dave

Thanks for the update, Hans. If there are further problems please let us know.

Regards,

Dave

unknown

Hi Dave,

we still are getting high loading times.

Our bigroom plan is build with 29 boards as issue source, we deselected all releases, placed about 27 epics in scope and load the plan with improved interface switched on = 15 seconds loading time of the plan.

That is a lof time, especially when the page reloads after changes.

We have dropped the issue at our vendor and are awaing their response.

Welcome!

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

Quick Links

Find more posts tagged with

server

advanced-roadmaps