What to avoid when creating views Follow

Views enable you to organize your tickets into lists using your ticket and user data. However, if you build a complex view with lots of conditions or a view that returns lots of tickets, you might be less than happy with the time it takes to load and display the view. View complexity and volume can result in slower performance.

When building view, make sure you avoid the following:

• Checking several text fields
• Checking for a null value, e.g. "Assignee is ( - )"
• Using broadly exclusionary conditions, e.g. "NOT" statements
  Instead use inclusive conditions being as specific as possible
• Checking for tags
• Checking for ticket description in a condition for "does not contain the following string/word"
  Checking for a string/word introduces greater complexity than checking for a tag
  Conditions that check for tags are preferred to as "the lesser of two evils" over those checking for a word/string

Remember that displaying a view involves searching all of the unarchived tickets to find matches for the conditions defined in your views. It’s always best to define views that look for what’s there, not for what’s not there.