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

Is there a way to speed up the user interface?

Andrew Paterson_hh1gcb

Dragging tickets from column to column on the Active board can be quite a frustrating process.

It takes a while (up to several seconds) for the landing column to appear once a ticket has been partially dragged with the mouse.

Scrolling up and down on a board is also quite frustrating as it will scroll a bit then wait for tickets to load in (again taking up to a second) then scrolling a bit more and waiting.

Now take both of these issues together and try re-ordering a ticket within a column. Ouch.

Accepted answers

Dan Breyen

Hi @Andrew Paterson could this be your issue? JSWCLOUD-26189

I found it on Atlassian's Jira page. If that is it, please vote for and watch it for future updates.

Here's another performance issue: JRACLOUD-73176

There may be a few others, but this is what I've found after a quick search.

Andrew Paterson_hh1gcb

The answer appears to be 'No'. There is no way to speed up the user interface.

I understand that 70 tickets is a lot but it is still a human number and can unfortunately happen even; if it is not a normal scenario or a best practice.

With that said we're back to a more normal number of tickets now and it still feels... clunky.

I had forgotten about the old interface and whilst it didn't look as pretty it was - at least as far as I can remember - a lot more responsive.

All comments

Dan Breyen

Hi @Andrew Paterson could this be your issue? JSWCLOUD-26189

I found it on Atlassian's Jira page. If that is it, please vote for and watch it for future updates.

Here's another performance issue: JRACLOUD-73176

There may be a few others, but this is what I've found after a quick search.

Rebekka Heilmann (viadee)

How many issues are appearing on your board? One solution might be to limit the number of visible issues to reduce loading times.

Andrew Paterson_hh1gcb

The answer appears to be 'No'. There is no way to speed up the user interface.

I understand that 70 tickets is a lot but it is still a human number and can unfortunately happen even; if it is not a normal scenario or a best practice.

With that said we're back to a more normal number of tickets now and it still feels... clunky.

I had forgotten about the old interface and whilst it didn't look as pretty it was - at least as far as I can remember - a lot more responsive.

Andrew Paterson_hh1gcb

Thanks @Dan Breyen I've voted on both those issues as they look similar to what is affecting the performance of my board. I had forgotten about the old interface but now I think about it it was considerably more responsive.

Andrew Paterson_hh1gcb

Hi @Rebekka Heilmann,there are 5 columns of which the longest has about 70 tickets in and maybe about 150 total tickets on the board.

Cheers,

Andrew

Rebekka Heilmann (viadee)

70 Tickets in one column is quite a lot for a board tbh so that might explain it. Imagine having 70 post its on a retro-inperson-whiteboard and trying to grasp the content of that in one go... The whole point of a board is having a quick overview.

Are old tickets cleared "away" automatically or manually? Is it actually one team working on the issues or could you split it?

Nic Brough -Adaptavist-

@Dan Breyen has already pointed to the bugs I would have mentioned, so I'm not going to repeat that bit.

But you might try simplifying your board.

Jira has to run many filters, many times, on a board, and each one imposes compounding work effort on the system. The more issues a filter returns, the more work it has to do.

A board is always based on a filter. The defaults, and the boards that use fixed filters you can't change are usually "Project = XYZ and issue is not 'done' for how this type of project defines it".

But boards then can run three more sets, possibly four!

I believe the "current content of a column" is not done as a JQL filter, but I'm not sure (that's the "possibly four")
Issue colours
Quick filters (these need to be run when loading or refreshing the board, not just when clicking on them)
Swimlanes

A board with 2 colours, 3 quick filters, and 4 swimlanes can be running 25 filters on any given operation, and all of those are slower the more issues they return.

If you can't simplify your filters for colour/swimlane/quick, then you should look to the volume. Try to reduce the number of issues. Do you really need 70 issues in a column? Probably not. 70 issues is getting towards the higher end of the number of issues you should have on a team's scrum or Kanban board entirely. (A scrum board would only show the current sprint, a Kanban - maybe yes 70 in "done", but you should probably be releasing well before you have 70).

Atlassian say boards really become unusable at 500 issues. I say you really start to suffer when going over 300 technically, but the humans probably start getting confused and lost before you hit 100 - it's just too much for a team to try to deal with in a sprint.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud