Test Cycle cannot be loaded because of caching previous search result in all browsers:
1. I am using Test Management For Jira
2. In the Test Cycle, I search a Cycle Name but its result cannot be returned (page keep loading with a circle)
3. From that moment, I - with my account - can work with Test Case, Test Plan but no Test Cycle anymore. I try to use different browsers, different machines but the same behavior.
I thought my Jira account is being tracked. So, the failed search result always keep there. I cannot work in Test Cycle from that moment.
Could you please help?
Thank you
Community moderators have prevented the ability to post new answers.
Hi @Diệu Phạm ,
Here are the steps to clear plugin cache.
If this does not fix and you are facing the issue in other areas of JIRA instances, you can do a reindexing as well.
Thanks,
Amith Mathur
Hi @Diệu Phạm ,
Plugin cache can be cleared from the server side only. As you are experiencing the issue in all the browsers, you need to clear the plugin cache. You can also try jira indexing.
Thanks,
Amith Mathur
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.
Unluckily, after asking help from server side. I cannot overcome my issue.
Observing closer to the console output. I am seeing the response 500 whenever navigating to Test Cycle. Detail is:
Request Method: GET
Status Code: 500
Remote Address: 127.0.0.1:8888
Referrer Policy: no-referrer-when-downgrade
Response Headersview source
Could you pls help?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Diệu Phạm ,
Can you please check the app vendor, Test Management For Jira? It appears it is coming from the app functionality.
Thanks,
Amith Mathur
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.
Wow: I wouldn't do ANY of that. Read this, instead: "Clear Groovy classloader or Jira internal caches"
This does implicate the app and the vendor, so there are probably variants on this action for other products.
I guess the point is that the client cache CAN be cleared, and you may need a script to perform the task (if the vendor doesn't have a workaround).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.