Support
Help with Baytek Agile Analytics for Jira
Reach the team behind Baytek Agile Analytics, learn what to include in a support ticket, and check the quick triage table before you write in — most setup questions are covered there or in the documentation.
Email support
Send a message to our support inbox. We reply within one business day.
support@baytekdev.comOffice hours
Monday to Friday, 9 AM to 5 PM Pacific Time. Tickets sent outside these hours are queued for the next business day.
Major outages are handled outside business hours when reported via the email above with “outage” in the subject line.
What to include in a ticket
The more of these you can include up front, the faster we can reproduce and fix what you're seeing.
App version
Open the app in Jira, then Configuration → General → About panel — copy the version string shown there.
Jira site URL
The full URL of your Jira Cloud site (for example, https://your-company.atlassian.net).
Project key
The Jira project key the issue is happening in (the short uppercase identifier shown in issue keys, like ABC-123).
Screenshot or screen recording
A picture or short clip of the view where the issue appears makes triage faster than a text description.
Browser and console errors
If you see a broken view, open the browser DevTools console (F12), reload the view, and paste any red error messages into the ticket.
Steps to reproduce
A short ordered list — open this view, click this button, expect X, see Y — is usually enough.
Common-issue triage
Quick first checks for the things we get asked about most often. Longer-form answers live in the documentation.
| Symptom | First check |
|---|---|
| Cycle time or flow metrics look wrong | Open Tools → Configuration and confirm your custom Jira statuses map to To Do / In Progress / Done. The default auto-discovery covers standard workflows; custom statuses need explicit mapping. |
| A view is empty or shows zero items | Confirm the project and sprint selected at the top of the screen — empty views are usually a project or sprint picker mismatch, not an app error. |
| Dashboard widgets show "Pro tier required" | Dashboard widgets are part of the Pro tier. Every new install gets a 30-day Pro evaluation through Atlassian Marketplace automatically. |
| Sprint Alerts not firing to Slack or Teams | Sprint Alerts run hourly. Confirm the webhook URL is configured under Configuration → Sprint Alerts, then wait for the next hourly cycle. Pro tier required. |
| Audit Trail entries missing | The audit trail keeps the most recent 200 configuration changes per project. Older entries roll off — this is by design and documented in the Privacy Policy. |
| A view loads slowly | Large projects with thousands of issues per sprint will take a few seconds. If a view consistently exceeds 30 seconds, open a ticket with the project key and sprint name so we can profile. |
Other resources
Documentation
Install steps, every analytics view explained, and the full FAQ.
Security overview
Forge-native hosting, read-only access, opt-in webhook egress only.
Privacy policy
What data the app accesses, how it's stored, and retention details.
Terms of service
License terms, restrictions, support scope, and liability notes.
Marketplace listing
Install or update the app from the Atlassian Marketplace.
Atlassian Community
Search broader Jira Cloud platform questions and Marketplace discussions.