Custom Field Manager is very slow

[Angelica Gavino]

Hi Team,

‌

The plugin is loading very slow. If I want to check the audit, I need to make sure that I do it during morning. During afternoon and more users have logged in to jira, it is super slow when loading (see snapshot – it will load like that for at least 15 minutes. or not load at all).

‌

I tried to download all the fields we have using the Download CSV option as well, but the process is taking soooo much time and no csv has been downloaded (we have 4400 fields). Not sure if it because of the volume of custom fields.

‌

More info about the plugin we have:

Installed version: 4.2.0 , Data Center

Jira: v8.5.9, Data Center

‌

[[ANS] Alexey Dorofeyev]

Hi @Angelica Gavino ,

Application load speed depends on a combination of many factors, such as the number of fields, the number of issues in your instance, the amount of system resources allocated for Jira, etc.
The information you provided is not enough to say for sure what the problem is. We can try to help if you provide us with the support zip file generated immediately after trying to download our application. How to generate this file is written in paragraph 3 of the Troubleshooting section of the documentation for our application: http://npe.systems/cft/docs/

[Angelica Gavino]

Thank you for the response.

I have generated the support zip but it is very huge that I can’t attach here. Is there a specific folder in that file that contains the relevant info so I can just share that instead of the whole file?

[Angelica Gavino]

The support zip is almost 70MB and I cant attach here (getting connection terminated)
i will be attaching the logs individually

[Angelica Gavino]

to reproduce the issue on our end : Cog > System > Custom Field Toolbox > Download CSV

after waiting for 15-30 minutes, we will get Connection was Reset. (attached)

‌

[[ANS] Alexey Dorofeyev]

Hi Angelica,

You have not attached the most recent file, which is simply called “atlassian-jira.log”. In any case, the support zip contains other files, besides the logs, that could be useful to us. Since most of the support zip is occupied by logs, you can try to remove from it all logs whose names do not contain "atlassian-jira.log*". If after that the archive is too large, leave only the files

• atlassian-jira.log
• atlassian-jira.log.1
• atlassian-jira.log.2
• atlassian-jira.log.3

‌

[Angelica Gavino]

Hi,

As requested, I attached only the zip that contains atlassian-jira.log*

[[ANS] Alexey Dorofeyev]

Hi Angelica,

I don't see any errors in the logs, so this is probably a performance issue. Since logging at the DEBUG level can seriously affect performance, try switching the logging level to ERROR and reopen the application page. If everything continues to be slow, please send the logs.

[Dale Keller]

We just upgraded to Jira version 8.5.11 and the custom field toolbox never returns it just appears to sit and spin. Is there a known issue?

[[ANS] Alexey Dorofeyev]

Hi @Dale Keller ,

At the moment, there is no specific issue that can lead to this behavior. Please send support zip (as described in paragraph 3 of the Troubleshooting section of the documentation for our application: http://npe.systems/cft/docs/) to our mail [e-mail].

[Dale Keller]

Hi Alexey,

The add-on worked until upgrading to Jira 8.5.11. I've started it a while ago in our test environment and it's still running. Here is what I see from the console. I will not be able to send the logs as the file is too big and blocked by our exchange servers. Is there another way to get it to you?

Regards,

Dale

[cid:[e-mail]6A00]

[[ANS] Alexey Dorofeyev]

@Angelica Gavino did you manage to solve your problem?

[[ANS] Alexey Dorofeyev]

@Dale Keller , it looks like the image is not attached.

As for the support zip, we need at least a log file that contains the moment when the application page is opened. Since it is just a text file, it shouldn't take up much space as an archive.