DaySignal for Jira
DaySignal Help
A daily Jira digest focused on what matters — today's live status, blockers, sprint health, and an optional email summary. Set up in two minutes.
Quick start
Open DaySignal from the Jira top navigation. The first time you visit, the welcome screen walks you through three steps. You can change every setting later via the Settings tab.
Schedule
Pick the days and time you want digests delivered. Default: weekdays at 9 AM in your timezone.
Personal Digest
Issues where you're Assignee, Reporter, or mentioned. Toggle on, hit Save.
Project Digest (optional)
Team blockers, sprint health, velocity tracking. Pick the projects you care about.
1. Schedule — click to enlarge.
2. Personal Digest — click to enlarge.
3. Project Digest — click to enlarge.
After your first Save, DaySignal begins backfilling overdue and at-risk issues for the projects you selected. The Loading data for newly-added projects banner stays visible while this runs — it's usually ready within 30 seconds. Velocity history takes up to one hour to populate.
What you see on first install
When you open DaySignal for the first time, a welcome card explains the 3 setup steps. Click Got it or the × close icon to dismiss it. Admins additionally see an Admin tip or Admin attention card based on whether the Story Points field was auto-detected.
The welcome card reappears automatically if the app is reinstalled. Once dismissed, it stays hidden for the rest of the install lifetime.
Personal Digest vs Project Digest
DaySignal has two digest modes, and most teams turn on both. They live on the in-app page as separate tabs and arrive in two separate sections of the daily email.
Personal Digest
Your work, across every project — what needs your attention today. Items appear if you're the Assignee, Reporter, or were mentioned in comments. Personal Digest is the right starting point for individual contributors and PMs alike: it tells you where to look first when you open Jira.
Personal Digest — your work across every project. Click to enlarge.
Project Digest
A team-wide view of one or more projects: what's blocking the team, what's overdue, what's at risk, what hasn't moved. Used by team leads, PMs, and anyone running a standup. You pick the projects via the Project Digest card in Settings.
Project Digest — top of the page with sprint health and Blocking section. Click to enlarge.
Project Digest — Overdue, At risk, and Stalled sections below. Click to enlarge.
Inside Project Digest, every issue is classified into exactly one of four sections by priority order:
- Blocking — issue blocks other work (linked as a
blocksdependency, or flagged as an impediment). - Overdue — past its due date and not yet done.
- At risk — due date approaching and may miss it.
- Stalled — no movement for several days; not captured by any section above.
An issue that fits more than one bucket goes into the highest-priority one (Blocking > Overdue > At risk > Stalled), with secondary context shown as small badges on the card. Each section lists up to 15 items by default; click Show more when you need the long tail.
Reading the project pills row
When you have multiple projects selected, a row of pills appears above the digest:
- All — combined view across every project. The badge shows the total of blocking + overdue + at-risk + stalled items.
- PROJECT-KEY pill (solid) — a project that already has data. The badge shows its problem count, or
✓if everything is clear. - PROJECT-KEY pill (dashed border +
…) — a project DaySignal is still backfilling. Click it to see a Preparing data empty state with anUpdatebutton.
Pending pills disappear automatically once backfill completes — usually within 5–30 seconds.
The Update button
If you've just added a project and the digest is empty (or shows the Preparing data state), click Update to re-fetch the latest data. It does not reload the page — it just re-runs the digest query.
You don't usually need to click it manually. DaySignal auto-refetches when you change project settings, navigate dates, or switch tabs. Update is only needed in edge cases: backfill is still running and you want to retry, or your team just closed an issue and you want fresh numbers.
Sprint Health
When Project Digest is enabled and your project uses Jira sprints, the page also shows a Sprint Health card per active sprint.
Sprint Health card — goal, Story Points done/remaining, at-risk count. Click to enlarge.
Read the card top-to-bottom:
- Sprint goal at the top — exactly as set in Jira.
- Story Points done / remaining — sum of completed SP versus what's still open in the sprint.
- At risk — count of issues in this sprint that the classifier flagged as at risk of missing the sprint end date.
- Capacity risk — surfaces when the remaining SP look too high for the team's recent velocity.
Velocity tracking only works once a Story Points field is configured for the instance. If your admin hasn't picked one yet, the Sprint Health card stays paused and shows an "Velocity tracking will stay paused" hint — see Troubleshooting below.
Mentions
If someone @-mentions you in a Jira comment, DaySignal pulls that issue into your Personal Digest the next time the digest builds. The mention shows on the issue card so you can tell at a glance why it's there — even if you're not the assignee or reporter.
Mentions are controlled by the Mentioned in comments filter in Settings → Personal Digest → Include issues where I am. It's on by default for new users. Turn it off if you only want assignee/reporter signal.
Settings reference
Open Settings via the gear icon at the top of the DaySignal page. Settings are personal — each user has their own copy, except Admin Settings (instance-wide).
Schedule
When digests are delivered. Applies to both Personal and Project digests.
Schedule card — days, timezone, delivery time. Click to enlarge.
| Field | What it does |
|---|---|
Send digest on | Days of the week. Default: Mon–Fri. |
Your timezone | The timezone used to interpret the delivery time below. |
Delivery time | Hour of the day to send the email. Default: 9:00. |
Personal Digest
Personal Digest — master toggle and inclusion filters. Click to enlarge.
| Field | What it does |
|---|---|
Enable daily digest | Master toggle for Personal Digest. Off = no Personal Digest is built or sent. |
Assignee | Include issues assigned to you. |
Reporter | Include issues you reported. |
Mentioned in comments | Include issues where you were @-mentioned in a comment. |
Watching | Include issues you're watching. Off by default — turn it on if you want watched issues to appear in your Personal Digest. v1.1 |
Project Digest
Project Digest — pick the projects to include and tune the Stalled threshold. Click to enlarge.
| Field | What it does |
|---|---|
Enable project digest | Master toggle for Project Digest. |
Project picker | Select which projects to include. You can re-pick at any time. |
Flag issues stuck for more than N days | Threshold for the Stalled section. Default: 3 days. Range: 1–30. |
Show planning-checks warnings (preview) | Surfaces orphan subtasks and active-sprint issues missing Story Points. Off by default. |
If a project uses a non-standard Story Points custom field, override it per-project here. Click to enlarge.
Admin Settings
Instance-wide configuration. Only Jira administrators can change these — non-admins see them as read-only.
Admin Settings — instance-wide Story Points Field selector. Click to enlarge.
| Field | What it does |
|---|---|
Story Points Field | Which custom field DaySignal reads for Story Points. Auto-detected on most instances; override here if your team uses a non-standard field. |
Save applies all changes at once. The button is right-aligned at the bottom of the page and is disabled until you've made a change.
Email digest
The same content you see in-app is delivered as a single daily email at the time you set in Schedule. One email per user — Personal items first, then Project sections if you have Project Digest enabled.
Personal Digest email — what an individual contributor receives. Click to enlarge.
Project Digest email — what a team lead or PM receives. Click to enlarge.
How to change frequency
Open Settings → Schedule. Uncheck the days you don't want, change the delivery hour, and Save. Changes apply on the next scheduled run — you don't need to re-install or reload anything.
How to turn email off entirely
Uncheck every day in Send digest on and Save. The in-app page keeps working — only the email stops. To turn DaySignal off completely, also disable Enable daily digest and Enable project digest.
Troubleshooting
Why is my Project tab empty?
Three common causes. (1) Enable project digest is off — flip the toggle in Settings → Project Digest. (2) No projects are selected — pick at least one in the Project picker. (3) DaySignal is still backfilling — when you add a project for the first time, the Loading data for newly-added projects banner shows in Settings, and a dashed-border pending pill appears in the Project tab. The tab fills in within ~30 seconds. If you don't want to wait, click Update in the per-project Preparing data empty state to retry. Velocity history takes up to one hour after backfill completes.
Where's the velocity / Sprint Health card?
Velocity needs two things: a Story Points field configured, and at least a few completed sprints to compute from. If your admin hasn't picked a Story Points field yet, you'll see an "Admin attention" message asking them to Configure now in Admin Settings → Story Points Field. After it's set, velocity history takes up to one hour to populate. If your project doesn't use sprints at all, the Sprint Health card simply doesn't appear.
How do I change which custom field is used for Story Points?
Only a Jira administrator can change this. Go to Settings → Admin Settings → Story Points Field and pick the right field from the dropdown. Non-admins see the same field but read-only — ask your Jira admin if it's wrong on your instance.
I'm not getting emails.
Check, in order: (1) Enable daily digest is on; (2) at least one day is checked under Send digest on; (3) the timezone matches where you actually are; (4) your inbox spam folder. The first email arrives the morning after you save settings — same-day delivery isn't supported.
An issue is in the wrong section.
Sections follow a strict priority order: Blocking > Overdue > At risk > Stalled. An issue can match multiple categories but lives in just one. The cross-context shows up as small badges on the card. If "Stalled" timing feels too aggressive or too lenient, raise or lower Flag issues stuck for more than N days in Settings → Project Digest.
I see "Admin attention" — should I worry?
No. It's a non-blocking informational message that the Story Points field couldn't be auto-detected. Personal Digest works without it. Project Digest works without it too — only the velocity / Sprint Health card stays paused. Pass the message to your Jira admin when convenient.
Privacy & data
DaySignal is a Forge app. That means it runs entirely inside Atlassian Cloud infrastructure — no data is shipped to third-party servers operated by us.
What permissions DaySignal requests
The following Atlassian scopes are listed in our app manifest and shown to admins on install:
read:jira-work— read issues, comments, statuses, assignees, due dates.read:jira-user— read user profile info (display name, account ID) for digest personalization.send:notification:jira— deliver digest emails.read:sprint:jira-software,read:board-scope:jira-software,read:issue:jira-software— read sprint, board, and agile-issue data for Sprint Health / velocity.
DaySignal does not request write access to Jira. We never modify, transition, comment on, or delete any of your issues.
What we store
DaySignal stores the minimum needed to build digests: your settings (toggles, schedule, project list), a tracking record of issues that changed recently, and a small cache of derived state for performance. All storage lives in Atlassian Forge SQL, hosted by Atlassian inside your tenancy.
Your onboarding-dismissed flag is stored in Forge SQL and cleared automatically when the app is uninstalled. Reinstalling brings the welcome card back.
What happens when you uninstall
Uninstalling DaySignal from your Jira instance is the off switch. Per the Atlassian Forge platform contract, all of an app's stored data is wiped when the app is removed — there's no manual cleanup step on your side. Reinstalling later starts a fresh state.
Contact
Need help, found a bug, or want to suggest a feature?
Email support@votazz.co or visit our support page — we read every message.