JIRA is not famous for its stellar performances, but it feels like it's becoming slower and slower with time...
For certain Use Cases, we even tend to use other tools, not because they fit better (on the contrary...), but only because they are faster.
To put it in a nutshell : are there some good practices to implement, in order to keep our instance in a good shape ?
(move closed ticket to another project, avoid boards with more than x tickets, split our "one project with several teams" organisation into "several projects", ..... ?)
Hi @Maël ,
I am not sure whether you have checked this or not - https://www.atlassian.com/software/jira/guides/getting-started/best-practices.
If you go through all the segments in this article, you would find Workflow, User and roles, Epics and Stories, Status and reporting, admin, automation and other best practices.
Please go through this and let me know if it helps.
Hi,
thanks for your prompt response. These are about processes and agile methods and the best way to use JIRA.
I don't see anything about optimizing the performances and making Jira faster ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.