1. Skip to navigation
  2. Skip to content
  3. Skip to sidebar

CodeSmith Insight

Table of Contents

Views

Some systems out there are either too rigid or too complex. CodeSmith Insight is both simple and dynamic, making it easy for you to organize your feedback. Under the hood, CodeSmith Insight is driven by an advanced search engine. Search is used to create dynamic views which allow you to view and organize your data the way you want to see it. This means that there are no rigid or restricting file structures or hierarchy, which means that everyone is free to search sort and view cases anyway they choose.

Views

A view is comprised of three things:

  1. Filter
  2. Auto Search
  3. View State

The filter is the a search query that determines what cases will appear in the view. These view filters are the key to organizing your data in CodeSmith Insight.

The auto search is a search query that runs against the selected row in a view, and then displays it's output in the east search box. This means that while you are navigating through items in your view, Insight can be automatically searching for similar cases. This is another way that Insight makes it easier for you to find cases related to what you are working on.

The view state determines what your view grid looks like. So while the filter determines what cases are in view, the state determines how they are displayed. This includes what columns are displayed, their order and widths, and even the sort order of the filter's search results. While a view does have a default state, each user is free to customize their view state to fit their needs.

Views inside of CodeSmith Insight include a complete permission system, which allows you to share read and write privileged with anyone that you choose.

View Tree

Views are organized by group in the View Tree, and your view tree contains a list of all views that you have access to.

A key feature of the view tree is the ability to drag and drop cases onto a node in the view tree, and then have that case's information updated to conform to the view. For example, if you were to drag a Feature Request on to a view that filtered cases of type Inquiry, that case would have it's type changed to Inquiry.