Hello. Kindly ask you for support, we use jira server 8.5.4 and service desk 4.5.4.
At the moment, we have several client portals. There are more than 160 request types in one of them and about 350 fields throughout the project. The portal actively uses follow plugin: script runner, element connect (nfeed) and extension. The portal often slows down request type and making new issue, plugins do not always work at right way. Have any recommendations or "best practices from atlassian" for the server version when configuring the self-service portal, regarding this case?
Also have you any recommendation about total quantity of issues on one portal?
Hello @Gulnaz Valieva I would suggest you start by doing clean up. As @Mathis Hellensberg you have plenty of issue types and most likely custom fields as well, I can't tell how many users you have but I've setup environments with less than 300 custom fields in which there were more than 3500 projects and 200.000 users.
What resources do you have on your server? Are you monitoring the performance with any monitoring tool that shows you are running short on resources?
Sounds like you should maybe look in to Data Center depending on the amount of users you have, but it sounds like quite a few! :)
I don't think I have ever seen an instance running that many request types for a single portal. Maybe you should look into merging some of them? I can't image the need or the reasoning behind having that many?
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.