The new dashboard is split into two groups - the action list and the watch list.

The action list shows alerts and action items that are sorted by priority, so you can handle them from top to bottom. It includes broken build and release pipelines, incoming pull requests, and work items. You can define your own priority rules in settings. The action list will not show any items that are in a good state and don't need your attention.

Use a watch list to keep track of things that you care about, but which are not actionable at the moment. By default, it includes builds that you recently started and pull requests that you have created. You can customize it to include things like tasks that you created for other people.

You can add multiple watch and action lists to the dashboard, to group things by project, team, or other criteria.

After configuring the dashboard, you can share it with your team. Any changes to shared dashboard settings will be propagated to other team members automatically.

CatLight v3 can work with multiple dashboards. You can use them for additional grouping by teams, projects, roles, and activities. For example, you can create a dashboard for the on-call person, and a separate one for other engineers.

On the dashboard, click on settings on any of the panels to configure item groups and priority rules.

Action list settings

Use the item groups section, to select specific things that you want to monitor (build and release pipelines, pull requests for repositories, work items). Then you can create priority rules that will apply additional filters to the item group. The dashboard panel will display items that match the rules.

Priority rule settings:

• Item group dropdown - this is the initial set of items that the rule will be applied to
• Item type selector (B, R, P, W) - you can narrow down the items in the group to only specific types (builds, releases, pull requests, work items)
• Severity filter - select only items that have specific severity (green, blue, yellow, red)
• Red severity - failed build or release pipelines, work items in the red category
• Yellow - partially succeeded build and release pipelines, work items in the yellow category
• Blue - pull requests, pending approvals for release pipelines, work items in the blue category
• Green - successfully completed builds and release pipelines, work items in the green category
• Last change since - this rule will only match the items that have changed in the specified interval. For example, if you put "7d" there, it will only select builds that have been completed in the past 7 days. This is useful if you want to filter out old branch builds, abandoned pull requests, and other things that you don't plan to act upon.
• Build filters (B)
• Only my builds - include only build pipelines that have builds started by the current user. 
• Branch filter regex - include only builds for branches that match the specified regular expression. If the branch cannot be determined for the build, the build will still match this rule. You can use this regex syntax to describe the rule, and regex101 to test your regex quickly. This setting is useful when you want to have different priorities for different branches. For example, it might be urgent to fix the broken build on the main branch of the project, but the same build on the feature branch is less important.
• Invert regex - the rule will select the build if it does not match the regex above.
• Pull request filter (P)
• Needs attention - this setting will include incoming pull requests that other people have created for the current user. It will also match pull requests that the current user has created, and that have votes and feedback from other users.
• Outgoing - will match pull requests that the current user has created. This is useful for the watch list panel.

Watch list settings

Watch list selectors are similar to action panel rules, but the priority of rules on the watch list does not matter.

Items on a watch list panel do not affect the status of the tray / menu bar app icon, but you will still get notifications about them.

Sorting

On the dashboard, items will be automatically sorted, depending on the panel type:

• For action list
• Items are sorted according to priority rules (an item that matches rule #1 will be above the item that matches rule #2)
• If they have the same priority, the oldest item will be at the top
• For watch list
• The most recently changed item will be at the top

To change the team:

1. In the CatLight app, click on the "Team" button, then on "Leave team".
2. Click on "Enable collaboration" button on the dashboard and select the new team to join. If you don't see the right team on the list, ask the team admin to add you to the team at https://service.catlight.io 

When your attention is needed, CatLight will show a solid icon    . The icon will match the color of the top item on the action list.

When something is broken, but you don't need to check it, the icon will change to an outline    . This happens when all items on the dashboard are being investigated or acknowledged.

When everything is good, the icon is green 

When focus mode is activated, CatLight will stop showing you notifications, and the icon will turn to .

Overall status	Icon	Build status	Release status	Pull request status	Other
Critical		Build failed	Release failed
Warning		Build partially succeeded (Azure DevOps/TFS)	Release partially succeeded		Cannot connect to the server
Info		-	Environment is pending approval	Incoming PR
Normal		Build succeeded	Release succeeded

When the build is being investigated, the tray icon will change to its acknowledged state for the whole team.

  =>  

Build investigation status is displayed on the dashboard.

After the build is fixed, the investigation will be automatically removed.

Build investigations expire in 24 hours. So, if someone pressed the button and forgot about it, CatLight will raise an alarm on the next day.

This feature is available for all continuous integration servers that we support. User need to be authenticated on the build server to see it.

 We divide branches in four categories:

• Primary - they will be always visible on the dashboard. They include branches like master, develop, trunk, etc.
• Short-lived - those are branches for pull requests. CatLight will show them for one day on the dashboard.
• Other - this is a category for feature, bugfix and release branches. They will be tracked while they are active, and had at least one build in the past week.
• Ignored - those branches will not be monitored. You can hide branches from previous categories by adding them to ignored.

By default, CatLight will show all active branches, but you can configure it to only show branches with your changes. Note for Jenkins and TeamCity: this feature is available only for authenticated users. If you connected using anonymous or guest account, please re-connect with your personal account to use it. 

You can configure regular expression that categorize branches in global app settings. Go to edit menu/settings to change them.

Use context menu  to hide specific branches from a dashboard:

Branches are supported across all platforms: TFS, VSTS, TeamCity, Jenkins, Travis CI and AppVeyor.

For Jenkins we also support Multi-branch plugin and GitHub organizational folders plugin.

Features:

• Notifications about the status of every release environment
• Separate notification when release is waiting for your approval
• Overall status and history on the dashboard
• Release investigations

You can use existing work item queries to select tasks and bugs that you want to monitor. Choose one of two modes:

• Show all - use this for queries that should return empty result when everything is OK, and for queues of short-term work. For example: “Important open bugs”, “Urgent tasks”, “Bugs to verify today”, “Bugs to review”.
• Show changes - use this to track changes in long-term queues of work, like “My tasks”, “Backlog”, “Recent bugs”

Each query can have a different level of importance:

You will get a notification when new work item matches the query. Catlight tray icon will also change color and stay that way until you acknowledge the changes.

Dashboard will show a list of work item query results. In “show changes” mode, it will only show work items that have changed since last acknowledgment.

If you don't see the query that you need, create it in TFS/VSTS and then you can monitor it in CatLight. Any user can add queries to "My Queries" folder. You may need project admin permission to add it to "Shared Queries" to share it with the team.

To change this, go to the edit menu/settings.

For long-term use you can make the following changes

• Notifications
  • Choose "My Builds" to see less notifications. You can still see the statuses of all monitored builds in the  tray.
  • Uncheck "Show notifications when I change a work item"
• Dashboard
  • Check "Don't show work item changes that I made myself"
• Branches
  • Choose "Track My Branches"

Next steps:

Configure accelerated notifications for Azure DevOps/TFS

Configure accelerated notifications for Jenkins

How to enable accelerated notifications

• Install the CatLight Azure DevOps extension from the Visual Studio Marketplace
• Go to Azure DevOps web UI. Every project should now have "CatLight" hub on the left. 

• In the CatLight hub, click on "Enable accelerated notifications". The hub will ask you for your CatLight team id. You can get it from the CatLight App-> Help and Feedback menu -> About. If you don't use CatLight yourself, and just want to configure accelerated notifications for other users, ask one of them to provide a CatLight team id for you.
• Accelerate notifications are now enabled for this Azure DevOps project. You can repeat the previous step for every other project you want to accelerate. The team id will be asked only once, but you can change it later in hub settings if needed.

You can check the CatLight app to see that accelerated notifications are working. On a dashboard, go to panel settings and edit any item group. You should see a yellow thunderbolt near the projects that have accelerated notifications .

How accelerated notifications work

CatLight extension for Azure DevOps can configure webhooks for specified projects. After that Azure DevOps server will make an HTTPS call to CatLight cloud service to notify it about completed builds/new pull requests and so on. The CatLight service will then forward the information about the changed item to the CatLight desktop apps. The CatLight service does not store any details about the changes, and forwards only the identifier of the changed item.

How to enable accelerated notifications

• Install the CatLight Jenkins plugin.
• Go to Jenkins web UI, and click on the CatLight link in the left bar. 

• Click on the "global settings" link, set a CatLight team id in Jenkins settings, and save them. You can get the team id from the CatLight App -> Help and Feedback menu -> About. If you don't use CatLight yourself and want to configure accelerated notifications for other users, ask one of them to provide a CatLight team id for you.

• Accelerated notifications are now enabled for this Jenkins server.

You can check the CatLight app to see that accelerated notifications are working. On a dashboard, go to panel settings and edit any item group. You should see a yellow thunderbolt near the projects that have accelerated notifications .

How accelerated notifications work

CatLight plugin for Jenkins will notify CatLight cloud service about started and completed jobs. The CatLight service will then forward the information about the changed item to the CatLight desktop apps. The plugin will send only the id of the changed job using HTTPS request. It does not send any job details. CatLight Jenkins plugin is open-source and you can contribute to it on GitHub.

Syntax:

• * - matches any number of characters
• ? - matches a single character
• […] - matches any of the enclosed characters. For example: [a-z] , [a-d1-9]
• ?(pattern-list) - Matches zero or one occurrence of the given patterns. pattern-list is a list of one or more patterns separated by a ‘|’. 
• *(pattern-list) - Matches zero or more occurrences of the given patterns.
• +(pattern-list) - Matches one or more occurrences of the given patterns.
• @(pattern-list)  - Matches one of the given patterns.
• !(pattern-list) - Matches anything except one of the given patterns

Examples:

• MyProject*Build
• +(Build|Release)
• +(MyProject|OtherProject)*Build
• !(temp)

For every user, this report will show the number of items in different states on their dashboards.

To add this report, go to teams menu > show team status.