Skip to content

Troubleshooting & FAQ

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

The AI concluded your request needs data or actions outside Spotlight’s current reach — for example sending emails, writing to Jira, or reading non-Atlassian systems.

Fix: rephrase toward what Jira data can answer (breakdowns, trends, tables, SLAs, access). Requests like this are also how we prioritize new data sources — tell us what you asked for at support@bytera.tech.

”Monthly AI budget reached” / “Your monthly AI limit reached”

Section titled “”Monthly AI budget reached” / “Your monthly AI limit reached””

AI drafting has monthly fair-use caps — 150 drafts per user plus a shared site budget of 1,000 AI calls (a draft normally uses one call, occasionally two when Spotlight automatically retries). The message tells you which cap you hit.

Fix: the caps reset monthly. Meanwhile the ten templates and the manual builder work without limits — only AI drafting is capped.

Jira rejected my JQL / “the query must restrict results”

Section titled “Jira rejected my JQL / “the query must restrict results””

Jira’s search API requires bounded queries. A query like ORDER BY key parses fine but is rejected because it doesn’t restrict results.

Fix: add a restriction — a project (project = PAY), a date window (created >= -90d), or a status filter. Spotlight dry-runs every query before saving precisely so you find this out now, not later.

The JQL is valid but returned nothing.

Most common cause: a status name that doesn’t exist on your site (e.g. status = Closed on a site whose done status is “Done”). Prefer statusCategory != Done / statusCategory = Done — status categories exist on every site. Test the query in Jira’s issue search to see what it returns.

You picked the Story points (sum) metric, but Spotlight couldn’t find a story points field (neither Story Points nor Story point estimate) on your site.

Fix: choose a different metric, or add story points to your projects (typically by enabling estimation on your boards).

Velocity shows “No closed sprints yet” or an error

Section titled “Velocity shows “No closed sprints yet” or an error”

The Sprint velocity source needs a Scrum board (Kanban boards have no sprints) and at least one closed sprint.

Fix: check the project key on the spotlight; confirm the project has a Scrum board with completed sprints. On a brand-new board, wait for the first sprint to close.

The access table says I have no access to a project

Section titled “The access table says I have no access to a project”

Jira only reveals role members to users with project-admin permission on that project — Spotlight always reads with your permissions and reports honestly where they end.

Fix: ask a project admin to view that project’s rows, or have them open the same spotlight (they’ll see the projects they administer).

Some of the plan’s per-item lookups failed; the notice shows how many, in which step, and the status codes.

  • 404 usually means the item legitimately has no such data — e.g. an SLA lookup on an issue that isn’t a JSM request.
  • 403 means your permissions don’t cover that item.

The rest of the report is real. If most lookups fail, the plan’s filter is probably selecting the wrong items — edit the plan or re-draft with a more specific description.

Either nothing has been shared on the site yet, or a site admin has restricted the View capability to groups you’re not in (see Settings).

I can’t share — or my save was rejected with a permission message

Section titled “I can’t share — or my save was rejected with a permission message”

A site admin has restricted the Publish capability to specific groups. Ask an admin to add your group on the Settings page.

Also note the gallery caps: 200 shared spotlights per site, 15 per author. If you’re at a cap, remove an old one first.

I want to make a private spotlight shared (or vice versa)

Section titled “I want to make a private spotlight shared (or vice versa)”

Visibility is fixed at save time. Changing private ↔ shared in place would silently move content between per-user and site-wide storage, so Spotlight makes it explicit instead: delete and recreate with the other visibility. Your description is on the card — reuse it as the AI prompt to rebuild in seconds.

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.

Does Spotlight work with Jira Data Center?

Section titled “Does Spotlight work with Jira Data Center?”

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

Where does the AI run, and what does it see?

Section titled “Where does the AI run, and what does it see?”

On Atlassian-hosted models (Forge LLMs) — inside the Atlassian platform, never a third-party service. It receives your description plus light site context (project keys and names, status names) and never issue data. See Draft with AI.

No. Spotlight requests no write scopes — the Jira REST access it holds is read-only by construction, and custom plans are additionally restricted to GET requests against whitelisted Atlassian endpoints.

  • 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.