Skip to main content

FAQ & Troubleshooting

Common questions and solutions for Dike users.

Frequently Asked Questions​

Installation & Setup​

How long does installation take?​

About 10-15 minutes for the complete setup:

  • Marketplace installation: 2-3 minutes
  • GitHub OAuth connection: 2 minutes
  • GitHub App installation: 2-3 minutes
  • Project setup: 2 minutes
  • Initial scan: 2-5 minutes per repository

Do I need to be a Jira administrator?​

Yes, initial installation requires Jira administrator access. After setup, you can delegate Dike administration to non-admins by granting them Dike admin permissions.

Can I test Dike before rolling it out to my organization?​

Yes. During GitHub App installation, select "Only select repositories" and choose a single test repository. You can expand access later.

Does Dike work with GitHub Enterprise?​

Dike works with GitHub.com (cloud). GitHub Enterprise Server (self-hosted) is not currently supported.

GitHub Connection​

Why do I need both OAuth and a GitHub App?​

They serve different purposes:

  • OAuth authenticates your personal account and shows which organizations you belong to
  • GitHub App provides access to repository data (commits, PRs, workflows) with granular permissions

Can I connect multiple GitHub organizations?​

Yes. After OAuth connection, you'll see all organizations you're a member of. Install the GitHub App on each organization you want to monitor.

What permissions does Dike need on GitHub?​

The GitHub App requests read-only access to:

  • Repository contents (commits, branches)
  • Pull requests and reviews
  • Workflow runs and status checks

Dike never writes to your repositories.

My organization doesn't show up in Dike. Why?​

Common causes:

  1. You're not a member: Verify your GitHub organization membership
  2. OAuth needs refresh: Disconnect and reconnect your GitHub account
  3. Organization restrictions: Some organizations restrict third-party app access. Contact your GitHub organization admin.

Compliance Checks​

How far back does Dike scan?​

By default, Dike scans the last 365 days of commits and pull requests. This provides comprehensive coverage without overwhelming you with historical data.

How often does Dike check for new violations?​

  • Every 5 minutes: Quick incremental check for new activity
  • Every hour: Deep compliance analysis

New violations are detected and Jira issues created automatically.

Can I exclude certain repositories or branches?​

Yes. In the Compliance Rules configuration:

  • Repository scope: Choose specific repositories or use "All repositories"
  • Branch patterns: Specify which branches to monitor (e.g., main, release/*)
  • File exclusions: Ignore specific paths using glob patterns

What's the difference between "missing issue key pattern" and "missing issue" checks?​

  • Pattern check (missing-issue-key-pattern): Looks for text matching PROJ-123 format using regex. Faster, but doesn't verify the issue exists.
  • Issue existence check (missing-issue): Verifies the referenced issue actually exists in your Jira instance. Catches typos but only works for the connected Jira.

Use the pattern check if you have multiple Jira instances. Use the existence check for stricter validation when all issues are in one Jira.

Why are example rules disabled by default?​

This lets you review and customize rules before they start creating violations. Enable rules in the Compliance Rules tab when you're ready to start monitoring.

Violations & Jira​

Where do violation issues get created?​

In the Jira project you created during setup (e.g., "COMPVIOL"). Each violation becomes a Jira issue in this project.

Can I customize the violation issue workflow?​

Yes. The violation issues use standard Jira workflows. You can:

  • Add custom statuses (e.g., "Under Review")
  • Add required fields or approvals
  • Configure automation rules

Can I delete violations?​

You can resolve or close violations in Jira, but we recommend keeping them for audit purposes. Resolved violations provide evidence of your compliance process.

Troubleshooting​

GitHub Connection Issues​

"Not connected" status after authorizing​

Symptoms: You authorized GitHub but Dike shows "Not connected"

Solutions:

  1. Clear browser cookies and try again
  2. Revoke Dike's access in GitHub Settings → Applications → Authorized OAuth Apps, then reconnect
  3. Check if your organization has OAuth app restrictions enabled

"App not installed" for an organization​

Symptoms: Organization shows but GitHub App is not installed

Solutions:

  1. Click "Install App" and complete the installation on GitHub
  2. If you don't see the install option, you may not have admin access to the organization
  3. Contact your GitHub organization admin to install the app

Repositories not appearing after GitHub App installation​

Symptoms: App is installed but repositories don't show in Dike

Solutions:

  1. Check repository selection: On GitHub, go to Settings → Applications → Installed GitHub Apps → Dike → Configure. Ensure the repositories you want are selected.
  2. Wait for sync: Repository discovery can take a few minutes
  3. Refresh the page: Sometimes a browser refresh helps

Scanning Issues​

Scan seems stuck or taking too long​

Symptoms: Progress bar doesn't move or scan takes more than 10 minutes

Solutions:

  1. Large repository: Repositories with extensive history take longer. Initial scans of very active repos can take 5-10 minutes.
  2. GitHub rate limits: If you're scanning many repositories simultaneously, you may hit rate limits. Scans will automatically resume.
  3. Refresh and retry: Refresh the page and click Rescan

No violations found but I expected some​

Symptoms: Scan completes but shows 0 violations

Possible causes:

  1. Rules are disabled: Check that your rules are enabled in the Compliance Rules tab
  2. Repository not in scope: Verify the rule group includes your repository
  3. Branch not monitored: Check that the rule's branch patterns match your branch
  4. Commits too old: By default, only the last 365 days are scanned

Violation Issues​

Violations created but no Jira issues​

Symptoms: Dike shows violations but corresponding Jira issues don't exist

Solutions:

  1. Check project configuration: Verify your Compliance Violations project exists and is configured correctly
  2. Permission issues: The Dike app user needs permission to create issues in the project
  3. Issue type missing: Ensure the "Compliance Violation" issue type exists in the project

Duplicate violations​

Symptoms: Same violation appears multiple times

Note: Dike has built-in duplicate detection. If you see duplicates:

  1. They may be for different commits/PRs with similar messages
  2. Check if rules were modified and re-triggered
  3. Contact support if the issue persists

Performance Issues​

Dike is slow to load​

Symptoms: Pages take a long time to load

Solutions:

  1. Browser cache: Clear browser cache and cookies
  2. Many repositories: If you have hundreds of repositories, filtering and loading takes longer
  3. Network issues: Check your network connection

Getting Help​

Support Resources​

  • Documentation: You're reading it! Browse the sidebar for detailed guides.
  • Atlassian Community: Search for Dike-related discussions
  • In-app feedback: Use the feedback option in the Dike interface

Reporting Issues​

When reporting an issue, include:

  1. Steps to reproduce the problem
  2. Expected vs actual behavior
  3. Browser and Jira version
  4. Screenshots if applicable
  5. Any error messages from the browser console

Feature Requests​

Have an idea to improve Dike? We'd love to hear it! Use the in-app feedback option or contact our support team.