Filter error

Hi All

I created a filter statement in jira as follows:

priority in (Highest-最高, Highest) AND (filter = 25667 0R filter = 25666 OR filter = 25669 OR filter = 25668 OR filter = 25670)

The displayed result is normal, but when I save and share with others, the interface prompts an error, as follows: When I visit this filter again, I also visit 500 errors, I would like to ask what is the specific reason

3 answers

0 votes

Hi Arno,

Do you have a lot of custom fields? And do those custom fields have a Context that identifies specific project(s) used by that custom field? I used to get 500 errors all of the time until I added a context to all of my custom fields to identify the project and/or issue type using the Custom Field.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

The page also should contain a stacktrace at the bottom with actual information.

If not, then also the {{ jira_home }}/log/atlassian-jira.log will contain the exception with the stacktrace to tell the story.

500 is such a generic error code that it can be anything, and you cannot do anything without the log, because the log (subsequently, the exception/stacktrace) is the only thing that can tell what happened.

Judging from the sticks, probably it's due to special characters, but again, it's a guess, the log knows more.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Radek Dostál

Thank you for your reply

I inquired in the log according to what you said, and did prompt an error. The error information is as follows

In addition, I checked each filter, and the JQL statement for one filter is (filter! = 20099 AND filter = 25366 AND filter ! = 23650 AND created < -60d), this filter access will prompt the same error, when I create a filter myself, use this query, I directly access the corresponding link (url/issues/? filter=26337), and an error message is also displayed, but I can find the corresponding result