Troubleshooting & FAQ

If your question isn’t covered here, email support@bytera.tech.

”No Scrum Board Found”

SyncUp only works with Scrum projects. Kanban-only projects and projects without any board can’t be analyzed because there’s no sprint to read.

Fix: add a Scrum board to the project (or use SyncUp on a different project that has one).

”No Active Sprint”

The project has a Scrum board but no sprint is currently active.

Fix: start a sprint from the project’s Backlog. SyncUp will pick it up automatically on the next load — no setting needed.

”License Required”

The app is installed but the Marketplace subscription has expired or been cancelled.

Fix: renew the trial / subscription from the Marketplace listing or Atlassian admin → Manage apps → Subscriptions.

SyncUp doesn’t appear under Apps

Possible causes:

App not fully installed — go to Settings → Apps → Manage apps in Jira and confirm SyncUp is Enabled.
Browser cache — hard-refresh (Cmd/Ctrl + Shift + R).
You’re not in a Scrum project — see “No Scrum Board Found” above.

The Daily Brief is empty / says I have no items

You see only the greeting and weekly stats, no Urgent / Focus / Waiting sections.

Cause: none of the issues in the active sprint are assigned to you.

This is normal — Developer view filters to your assigned items. Scrum Masters and Product Owners see team-wide views instead.

My role looks wrong

A project admin assigns roles in Settings → 👥 Team Roles. SyncUp does not auto-infer roles from Jira project roles.

Fix: ask a project admin to update your role. New users default to Developer.

Reports tab is empty

The Reports tab only contains autopsies for sprints that closed while SyncUp was installed. We don’t reconstruct history from before installation.

Fix: wait for your next sprint to close. The autopsy will appear within minutes.

Velocity Trend doesn’t show / shows fewer sprints than expected

The Velocity Trend in the Product Owner brief needs at least 2 closed sprints to draw a direction; it shows up to the last 5. If you’re missing recent sprints, check the Reports tab — every report there feeds the velocity view.

The daily email briefing didn’t arrive

Walk through, in order:

Settings → 🔔 Notifications: Daily Briefing toggled on?
Standup Hour correct? Hour buckets are 07:00–14:00.
Timezone correct? The hourly cron fires every hour; the email is sent only when the current hour matches the standup hour in your selected timezone.
Jira Email Notifications toggled on?
Hit 📧 Send Daily Brief to test the channel right now. If that works but scheduled doesn’t, the schedule settings are off.
Check the recipient’s Jira personal notification preferences — Atlassian sends emails via standard Jira issue notifications; if the recipient has those off, they won’t receive briefings either.

SyncUp shows scope creep when none happened

The Scope Creep alert and the Scope Stability score compare current scope with the earliest snapshot of the sprint. Snapshots are captured hourly. If SyncUp was installed after the sprint started, the earliest snapshot is from install time — not sprint start — so additions before install won’t show as “scope creep” and additions after might inflate the number.

Mitigation: install SyncUp before the sprint starts. After one full sprint with SyncUp installed, the numbers stabilize.

Forecast keeps swinging

The forecast is based on the current daily rate. Early in a sprint (especially the first 30%) the daily rate is noisy because few items have been completed. The Sprint Goal Risk alert intentionally doesn’t fire before 30% of sprint time has elapsed for this reason.

Mitigation: treat early-sprint forecasts as directional only. The forecast becomes reliable around the 30% mark and stabilizes through the back half.

Why does SyncUp need `write:jira-work`?

The write scope is used only to create a single internal “anchor” issue that SyncUp uses to deliver email notifications via Jira’s mailing system. SyncUp does not modify your team’s issues, comments, or workflows.

Forge has no SMTP. Routing email through Jira’s notification infrastructure is the standard pattern for Forge apps that need to email users.

Does SyncUp work with Jira Data Center?

No. SyncUp is a Forge app and runs only on Jira Cloud.

Does SyncUp track story points?

Velocity is currently tracked in issue counts, not story points. Two well-pointed teams might have similar issue counts but very different “real” velocity. If story-point tracking is important for your team, tell us — it’s a likely future enhancement.

How do I get more help?

Email: support@bytera.tech
Feature requests: reply to any support email with Feature request: in the subject

Changelog — what’s new and what’s coming.