• filters owned by the user.
• filters shared with a group that the user is a member of.
• filters shared with a private project that the user has Browse projects project permission for.
• filters shared with a public project.
• filters shared with the public.

If you don't see any Jira filters in CatLight monitoring settings, try saving a new filter in Jira. You will be its owner, and it should be displayed afterward.

• In the organization dropdown, select "All accessible organizations"
• Either provide a "full access" scope, or more granular access that should include:
  • Build - Read and execute
  • Code - Read, Status (for getting pull requests)
  • Graph - Read
  • Identity - Read
  • Project and Team - Read
  • Release - Read
  • Test management - Read
  • User Profile - Read
  • Work Items - Read and Write
• You can set a long expiration time to avoid repeating this process frequently (e.g. 1 year)

In the CatLight app, use a personal access token instead of a password, and keep the user name empty.

Here is how you can collect them:

1. Go to edit menu/settings/advanced and check "Enable extended logging". This will turn on the logging of requests and responses from the server. Sensitive data will be masked.
2. Repeat the action you had trouble with (e.g. connecting to a new server).
3. Click on "Help & feedback" menu -> Send diagnostic report to support

See also:  information about CatLight log files.

If you don't get any toast notifications from CatLight, try disabling it by searching for "Focus assist" in the Windows search menu, and then turning it off.

If you have "Priority only" option selected, you can click on "Customize priority list", and add CatLight app to it.

This usually happens when the user has multiple Microsoft accounts(e.g. personal and work accounts), and the wrong account gets used during connection.

CatLight uses the default web browser to authenticate to Azure DevOps. This browser can have a different Microsoft account authenticated in it. For example, you use Chrome in day-to-day work and sign in using a work account there. But, the default browser is Internet Explorer or Safari, and it might have your personal Microsoft account authenticated in it.

Resolution

1. In a default web browser, go to the Azure DevOps website (https://dev.azure.com/your-account-name) -> click on User settings -> Profile -> Authorizations. Then remove "CatLight" from there, if it is present.
2. In a default web browser, sign out of your Microsoft account.
3. Try to connect again from CatLight. You should be prompted to authenticate using a Microsoft account.

Workaround

As a workaround, you can try connecting using a personal access token (PAT): 

1. In Azure DevOps, click on your user picture in the top right -> Security -> Personal access tokens -> New Token.
   • In the organization dropdown, select "All accessible organizations"
   • Either provide a "full access" scope, or more granular access that should include:
     • Build - Read and execute
     • Code - Read, Status (for getting pull requests)
     • Graph - Read
     • Identity - Read
     • Project and Team - Read
     • Release - Read
     • Test management - Read
     • User Profile - Read
     • Work Items - Read and Write
   • You can set a long expiration time to avoid repeating this process frequently (e.g. 1 year)
2. In the Catlight app, create a TFS connection (not Azure DevOps) and use the following address:
   https://dev.azure.com/your-account-name (or https://your-account-name.visualstudio.com/ , depending on how it is displayed in your browser).
3. Uncheck "automatic configuration".
4. Past the PAT token into the password field.

If the workaround did not work for you, you can check out the logs for more details, or open a support ticket, so we can troubleshoot the issue.

Location of configuration files on different platforms

Windows:

%appdata%\Catlight\Data

Mac OS:

~/Library/Application Support/Catlight/Data

Linux: 

~/.config/Catlight/Data

Logs are written in two groups of files: 

• Log.txt – this is the log file of the background process that contains most of the app logic. It is usually the most useful, so check it first.
• TrayLog.txt – this is a log file of the UI process. If the application does not start, this log can contain details about the problem.
• NetworkLog.txt - trace of HTTP requests and responses between the app and your server. They can contain additional error messages from the server, and can be used to troubleshoot complex cases. To enable network logging, go to edit menu/settings/advanced and check "Enable extended logging".

Windows

Logs location:

%AppData%\CatLight\logs

Mac OS X

Logs location:

~/Library/Application Support/Catlight/logs

This is a hidden folder, but you can open it using the "Go to" menu item in Finder.

Linux

Logs location:

~/.config/Catlight/Logs

Add this certificate as trusted to resolve the problem, and try connecting again.

Instructions for Windows:
https://blogs.technet.microsoft.com/sbs/2008/05/08/installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista/ 

For OS X:
http://www.robpeck.com/2010/10/google-chrome-mac-os-x-and-self-signed-ssl-certificates 

For Linux:
http://askubuntu.com/questions/530056/install-root-certificate-on-ubuntu-14-04-64-bit