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

JIRA Software (Cloud) is difficult to use - it is extremely slow.

ian_finlay

Working with a team in India, they have remarked that JIRA Software (Cloud) is difficult to use as it is extremely slow. I am having response issues here in the Metro NY area, so I can only imagine how difficult it is for them.

Do I have any options?

Thank you

Regards

Accepted answers

All comments

Hernan Halabi - Elite IT Consulting Group

Hello @ian_finlay I manage lots of cloud environments and performance degradation isn't an issue in any of them. Nevertheless, sometimes certain apps can perform worse than others and affect the overall user experience. Also it would be expected that Jira behaves slow on an agile board with 500 issues in it. Is the poor performance happening everywhere or when using certain features of the tool? If it's everywhere then open a case with Atlassian to see what they see on their end, if it's only in certain pages then it might be a functionality that is causing this experience

ian_finlay

Hi Hernan - thank you for your response. I may not be describing our set up well, I'm new to JIRA and to Agile as well. In our main project we have a total of approx 1,500 (500 Closed) issues spread across maybe 10 sprints.

The active sprint has approximately 200 items. I spend most of my time in the issue view updating bugs and writing User Stories / Test cases.

Fully loading a bug by clicking on the link in a filter can take 2-5 seconds, this does not sound like a lot but I might process 60 issues in a day and it slows me down. My Indian colleagues have even slower times (I will get some accurate numbers from them).

Is this performance typical, will I just have to live with it?

Thank you for your help.

Best Regards

Ian

Hernan Halabi - Elite IT Consulting Group

No but it could be due to the amount of tickets in the active Sprint. I suggest you split the board into a few more board. Maybe a few kanban boards that all show the active Sprint but add an extra criteria (one board per priority for example). Doing this you will reduce the amount of cards in the board and I would expect that improves the behavior.

ian_finlay

Ok, thank you. I will suggest to the person in charge of our system design. I have to confess that it seems odd to me that spreading the issues over multiple boards would help the performance in the issue view. Is there a document you can point to that would help me understand?

I appreciate your help

Thank you

Ian

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-cloud

performance

atl-orange