Last updated: .
SmartDash, dashboards, charts and reports for Jira Cloud and Jira Service Management, runs entirely on Atlassian Forge. It adds widgets to Jira’s own dashboards and, in the Advanced edition, dashboards and role pages of its own.
What it stores
SmartDash keeps dashboard setups and settings, never work items. Numbers and work items are read from Jira each time they are shown.
SmartDash stores data only in Atlassian Forge hosted storage, which Atlassian provisions per site installation, and in Jira itself. SmartDash has no external database, file store or backup of its own. What it keeps in Forge storage is configuration: dashboard setups and their searches, who they are shared with, site settings, per-person favourites, recent lists and layouts, the list of Jira dashboards that use SmartDash widgets, and the names of each project’s issue types and fields. It does not keep work item summaries, descriptions, comments or field values. A widget’s settings on a Jira dashboard are saved by Jira with that dashboard, like any Jira gadget’s settings.
People are kept by their Atlassian account id only, never by name or email. Names are looked up from Jira, as the person viewing, each time they are shown.
Retention and deletion
Both editions
| Data | Where | Retention |
|---|---|---|
| A widget’s settings on a Jira dashboard (its search, chart type and options) | Jira, with the dashboard | Like any Jira gadget’s settings: until the widget or dashboard is removed in Jira |
| Where SmartDash is used: for each Jira dashboard with a SmartDash widget, its id, widget titles and kinds, and the search text each uses (account ids in it replaced), for site admins | Atlassian Forge hosted storage (the customer’s installation) | For as long as the app is installed, or until it is deleted in SmartDash |
| Migration records: for each dashboard copied, the id of the copy, what moved and what was left out, the time, and the account id of the admin who ran it | Atlassian Forge hosted storage (the customer’s installation) | For as long as the app is installed, or until it is deleted in SmartDash |
| Dashboard designs a person saves (visible only to them, at most five each) | Atlassian Forge hosted storage (the customer’s installation) | Until that person deletes them, or the app is uninstalled |
| Site settings chosen by admins, including whether AI help is on | Atlassian Forge hosted storage (the customer’s installation) | For as long as the app is installed, or until it is deleted in SmartDash |
| A person’s own last results (work item data they could already see), so a dashboard appears at once | That person’s browser, for that person only | At most 48 hours and at most 200 results. Not cleared by uninstalling the app: they stay until the browser’s site data is cleared or they expire |
Advanced also keeps
| Data | Where | Retention |
|---|---|---|
| Each SmartDash: title, widgets with their searches and options, look, owner’s account id, who it is shared with, which projects an admin approved for Share project data, and when it was created, changed and opened | Atlassian Forge hosted storage (the customer’s installation) | Until its owner deletes it, or the app is uninstalled. Archiving only hides it from lists |
| The last 50 visitors of each SmartDash, as account id and time | Atlassian Forge hosted storage (the customer’s installation) | Older entries are replaced as new visits come in |
| Per person: favourites (up to 200), recently opened SmartDashes (up to 20) and a short counter that limits how fast dashboards are created | Atlassian Forge hosted storage (the customer’s installation) | For as long as the app is installed, or until it is deleted in SmartDash |
| Per person: their own layout of a shared SmartDash (positions only) | Atlassian Forge hosted storage (the customer’s installation) | Removed after 90 days unopened |
| Per project: key and name, kind, names of its issue types, whether it uses sprints, and the names of its SLA and story points fields. Names only, never work items | Atlassian Forge hosted storage (the customer’s installation) | Refreshed when Jira says the project changed; removed when the project is deleted |
| Counters that limit AI help and Rovo use per person and per site | Atlassian Forge hosted storage (the customer’s installation) | Removed after two hours (hourly counts) or two days (daily counts) |
SmartDash keeps no backup or archive of Jira content outside Atlassian. Exports are files a person downloads: a SmartDash export holds its setup only; a CSV holds work items that person can already see in Jira.
Deleting data
- Delete a SmartDash (Advanced). Its owner can delete it. Work items in Jira are never changed or deleted by SmartDash.
- Closed Atlassian accounts. Each week SmartDash reports the account ids it holds through Atlassian’s Personal Data Reporting API. For every account Atlassian reports as closed, SmartDash erases that person’s own settings, favourites, layouts and saved designs. A SmartDash the person owned keeps only their account id and is shown to admins as having no active owner.
- Remove a widget. Removing a SmartDash widget from a Jira dashboard removes its settings with it, in Jira.
- Uninstall the app. Atlassian removes the app’s Forge storage under its platform lifecycle, on Atlassian’s schedule; Atlassian documents that hosted storage is retained for 28 days after uninstallation before it is deleted. After uninstall SmartDash cannot read it. SmartDash does not itself purge storage at uninstall; the platform does. Uninstalling cannot reach a person’s browser, so the browser copies described above stay until they expire or the browser’s site data is cleared.
- Data deletion requests. Contact us through the contact page. We will act on a verified request within 30 days. Data held by Atlassian follows Atlassian’s policy.
- Site deletion. When a Jira site is deleted, Atlassian’s site retention applies to the site and the app’s data; app data is deleted when the site is permanently removed.
Data residency
According to Atlassian’s Forge documentation, Forge hosted storage is data-residency enabled: it is held in the location of the host Atlassian product and moves with it when an administrator migrates the product. SmartDash sends no data to another location.
Architecture
SmartDash runs entirely on the Atlassian Forge platform. SmartDash does not operate any server, database or storage of its own: no customer data is processed or stored outside Atlassian infrastructure by SmartDash.
Data flow
- A person opens a Jira dashboard with a SmartDash widget, or a SmartDash page. Forge renders it inside Jira, in that person’s browser.
- While a widget or page is on screen, it asks SmartDash’s Forge functions for its numbers through the Forge bridge. Nothing is read for a widget that is off screen.
- The functions read Jira through the Jira REST API as the person looking, so Jira’s own permissions decide what comes back. A viewer with access to fewer projects sees fewer work items.
- The functions read and write SmartDash’s own data (dashboard setups, sharing, settings, per-person favourites and layouts, project names) in Forge hosted storage. Work items are not stored there.
- The browser keeps that person’s own last results for at most 48 hours, so a dashboard appears at once and then refreshes. These copies are never shown to anyone else.
- In Advanced, when someone asks for AI help, the functions send their words and names from the site to Forge LLM, a model hosted by Atlassian. Work items are never sent. See AI.
When SmartDash reads with its own access instead of the viewer’s: only in three cases. In Advanced, a Jira admin or project admin can turn on Share project data for one SmartDash and one project; that SmartDash then reads that project with the app’s own access, limited to the approved projects, so the people it is shared with see that project’s numbers. It is off until an admin turns it on. SmartDash also reads a project’s names (its kind, issue type names, whether it uses sprints, its SLA and story points field names), never its work items, and once a week checks whether the owners of SmartDashes still have active accounts.
Network diagram
| From | To | Protocol | Authentication | Notes |
|---|---|---|---|---|
| Person’s browser | Jira (Atlassian) and the SmartDash pages and widgets inside Jira | HTTPS | Atlassian user session | SmartDash pages are rendered by Forge inside Jira |
| SmartDash page or widget | SmartDash Forge functions | Forge bridge, HTTPS | Forge, with the signed-in person’s identity | Atlassian-managed |
| SmartDash Forge function | Jira Cloud REST API of the same site | HTTPS, via Forge’s managed client | Forge-managed, as the viewer; as the app only for Share project data, project names and the weekly owner check | No credentials held by SmartDash |
| SmartDash Forge function | Forge hosted storage | Atlassian internal, Forge-managed | Forge | Per-installation scope |
| SmartDash Forge function (Advanced) | Forge LLM | Atlassian internal, Forge-managed | Forge | Only when someone asks for AI help |
SmartDash makes no connection to any non-Atlassian host. Its app manifest declares no outside address (no egress), and there is no SmartDash-operated server, load balancer, database, queue, analytics service or third-party API in the architecture.
Encryption and the browser
The text that applies to every app is in Encryption at Rest. What follows applies to this app only.
So that a dashboard appears at once, a person’s browser keeps the last result of each widget they opened: work item data they could already see, for at most 48 hours, and never shown to anyone else. This copy is held by the browser on the person’s own device; it is not Forge storage and the platform encryption does not describe it. It is protected as that device and browser are. Uninstalling the app cannot reach a browser, so these copies stay until the browser’s site data is cleared or they expire.
SmartDash stores no API key or other secret. The AI in Advanced is hosted by Atlassian and needs no key of its own.
Logging
The text that applies to every app is in Data Logging and Retention. What follows applies to this app only.
The open counts and recent visitors that a SmartDash shows its owner are kept in Forge storage and shown only inside the app. SmartDash keeps Forge platform logs only. Its Forge functions write a line when something fails: for example when Jira gives an answer SmartDash did not expect, or when a background job (project names, weekly housekeeping) cannot finish.
What a log line may contain: operational data only: a short description of what failed, the error message, HTTP status codes, the type of widget or the name of the Rovo action that failed, and a few lines of the program’s own stack trace. Error text returned by Jira for a failed call can echo part of a request, such as a search.
SmartDash does not deliberately log work item summaries, descriptions, comment bodies, field values or the words a person types for AI help, and it holds no access tokens, API keys or secrets that could be logged.
Lines are written for failures; normal use writes no log line. The one exception is the weekly personal data report, which writes one line with counts only (how many accounts were reported, closed and erased), never account ids.
Subprocessors
The text that applies to every app is in Subprocessors. What follows applies to this app only.
SmartDash sends Jira data only to the Jira Cloud APIs of the site it is installed on, and to the browser of the person looking. Its only subprocessor is Atlassian (Forge hosting, storage and logs; and, in Advanced, Forge LLM for AI help).
| Party | Role | What it receives | Location |
|---|---|---|---|
| Atlassian (Forge platform and Jira Cloud) | Infrastructure and product provider: runs SmartDash’s functions, queues, storage and logging; hosts Jira | Everything SmartDash processes | Per Atlassian’s Forge documentation, Forge hosted storage is kept in the location of the host Atlassian product |
| Atlassian (Forge LLM), Advanced only | Hosts the AI model used for AI help | Only when someone asks: their words and names from the site, never work items (see AI) | Within Atlassian, under Atlassian’s terms for Forge |
The Standard edition does not use Forge LLM. SmartDash’s Rovo agent (Advanced) answers Rovo, Atlassian’s own AI, as the person asking, with dashboard titles, widget titles, counts and chart labels they can already see; what Rovo does with that answer is covered by Atlassian’s terms.
Declared outbound (egress) domains: none. SmartDash’s app manifest declares no outside address, so Forge does not let it call any host outside Atlassian. All its calls use Forge’s managed Jira clients, Forge storage and Forge LLM, which need no declared domain. SmartDash is eligible for Runs on Atlassian.
Software dependencies: Atlassian Forge packages and a small number of libraries bundled into the app (for example DOMPurify, which cleans ticket descriptions before they are shown). None is a hosted service and none receives data from SmartDash over a network.
Security and safeguards
The text that applies to every app is in Security and Incident Response. What follows applies to this app only.
Besides the responsibilities every app has, SmartDash is responsible for the permission checks in its functions. SmartDash requests only the Jira permissions (scopes) listed in its Marketplace listing and at installation, declares no outside address, and makes no call to a non-Atlassian host. Fix targets are in Vulnerability Reporting.
Built-in safeguards
- Reads as the viewer. Widgets and pages read Jira as the person looking, so Jira’s permissions apply. The app reads with its own access in three cases only: Share project data in Advanced, which a Jira admin or project admin turns on for chosen projects and which is limited to those projects; a project’s names (its kind, issue type names, whether it uses sprints, its SLA and story points field names), never its work items; and a weekly check of whether the owners of SmartDashes still have active accounts.
- Account ids only. SmartDash stores people by their Atlassian account id, never by name or email. Names are looked up from Jira as the person viewing, each time they are shown. Each week SmartDash reports the account ids it holds through Atlassian’s Personal Data Reporting API and erases the settings of any account Atlassian reports as closed.
- No changes to work items. SmartDash has no permission to create, edit or delete work items, projects, fields, users or groups. It creates Jira dashboards in two cases only, always as the person asking: an admin’s copy of a dashboard on the Migration tab, and a new private dashboard requested through SmartDash’s Rovo agent in Advanced.
- Admin actions checked on the server. Each admin action is checked again by SmartDash’s functions, not only hidden in the page.
- Hidden when not shared. A SmartDash a person may not open gets the same “not found” answer as one that does not exist.
- Ticket content cleaned. The description and comments of a ticket opened from SmartDash are cleaned with DOMPurify: scripts, styles, forms and frames are removed.
- Pasted text stays text. Text people type or paste, such as widget titles, descriptions and requests to the AI, is shown as text and never run as code.
- Safe spreadsheets. In CSV exports, cells that start like a spreadsheet formula are made harmless, so opening the file cannot run anything.
- AI that cannot act on its own. In Advanced, the AI’s answer is read as text and checked against fixed lists before anything changes. See AI.
- Rate limits. AI help is limited to 20 requests per person per hour and 400 per site per day; Rovo actions to 30 per person and 300 per site per hour.
Incidents
SmartDash follows the incident response plan. For SmartDash, an incident is any event that degrades or interrupts SmartDash’s service (widgets or pages fail to load, numbers wrong or not shown, AI help unavailable in Advanced), or that puts customer data at risk (suspected unauthorized access, a viewer shown data Jira would not let them see, cross-tenant exposure, data corruption).
| Severity | Examples |
|---|---|
| SEV1 Critical | A viewer shown work items Jira does not let them see; cross-tenant data exposure; widgets and pages fail to load everywhere |
| SEV2 Major | One widget type fails to load; numbers shown late or not refreshed |
| SEV3 Minor | One chart option not applied; wrong label in the UI |
A fix is verified on a real Jira dashboard and SmartDash page before the incident is closed.
Accessibility
The company statement is in Accessibility Statement. This is SmartDash’s second review of how accessible its screens are, against WCAG 2.2 Level A and AA, made on 15 November 2026 on development build 2.5.0. It is a self-assessment by the SmartDash team, not an independent audit and not a certification. Of the 55 criteria, 34 are rated Supports, 9 Partially Supports and 12 Not Applicable; none is left Not Evaluated. No screen reader has been used yet.
The fixes below are in production: the code evaluated as development build 2.5.0 is in production version 3.2.0 since 15 November 2026. It was not checked again in production.
Problems found during this review and fixed
- Menus (More actions, Ideas, Switch chart, Size) can be used with the keyboard: focus moves to the first item, the arrow keys, Home and End move between items, and focus returns to the button when the menu closes (2.1.1, 2.4.3, 4.1.2).
- Focus rings that were invisible on the current tab and on a project tag’s × now meet 3:1 (2.4.7, 1.4.11).
- Field edges in five of the optional styles, and on several boxes in every style, now meet 3:1 against the page (1.4.11).
- Accent-coloured text in three optional styles, and late and at-risk text in one, now meets 4.5:1 (1.4.3).
- While a dashboard is being prepared, the widgets under the overlay can no longer take focus (2.4.11).
- After a dashboard is created or opened, focus goes to its name (2.4.3).
- At 320 px and with text spacing, My view no longer scrolls sideways, and work item and project names wrap instead of being cut (1.4.10, 1.4.12).
- On/off switches always state on or off; the widget options button is announced as what it is (4.1.2).
- The work item count link in the Filters widget is at least 24 by 24 px (2.5.8).
- A held Enter key on Delete can no longer also confirm the deletion (3.3.4).
These checks were made on every widget and every Advanced page at 1280, 640 and 320 px, with the WCAG text spacing, in all twelve optional styles. The automated scan reports no problem on any of them after the fixes.
Known gaps
- In a narrow chart with text spacing applied, legend names can end in “…”. The full name is in the value card, the hidden data table and the CSV download (1.4.12).
- In Time in Status, the number of stays per status is shown only on hover; time and the number of work items are shown as text (1.4.13, 2.1.1).
- At 640 px, the Cancel and Save bar of the settings pop-up can cover part of a tall, focused JQL box, never all of it (2.4.11).
- Neighbouring chart colours are not 3:1 against each other. Every value is also given as text (1.4.11).
- Going back in the More actions menu puts focus on the first item, not the one you came from (2.4.3).
Questions or feedback about accessibility: the contact page, with the subject “SmartDash accessibility”. Say which screen or widget, what you use (for example a screen reader, keyboard only or zoom) and what happened. We reply within 3 business days.
Accessibility Conformance Report (VPAT 2.5, WCAG edition)
| Item | Value |
|---|---|
| Name of product | SmartDash for Jira, by Limbus Lab |
| Product version evaluated | SmartDash development build 2.5.0; second review. The same code is in production version 3.2.0 since 15 November 2026. |
| Report date | 15 November 2026 |
| Product description | An Atlassian Forge app for Jira Cloud. SmartDash adds chart, list, time-in-status, calendar and filter widgets to Jira dashboards (Standard), and in Advanced also its own dashboards, role pages (My view) and an AI box hosted by Atlassian. |
| Contact information | Limbus Lab, through the contact page (limbuslab.com/contact/) |
| Evaluator | SmartDash team, self-assessment (automated scans, measurements and keyboard walks in Chrome, part inside Jira; no screen reader) |
| Applicable standard | WCAG 2.2 Level A and Level AA. WCAG 2.1 Level A and AA criteria are a subset of these tables. 4.1.1 Parsing is obsolete in WCAG 2.2 and is not listed. Level AAA, Revised Section 508 and EN 301 549 tables are not included. |
| VPAT template | VPAT 2.5 (WCAG edition), ITI terminology |
Evaluation methods used
This report is a self-assessment that combines the following. It is not an independent audit.
- A test setup with the real SmartDash code of this build and made-up data, in Chrome: every widget (Chart as donut, stacked bars, line and tiles; List; Time in Status; Calendar; Filters), every widget’s settings, and every Advanced page (My view with three roles, All dashboards, New dashboard, a SmartDash dashboard, the settings page and the AI box).
- Each page at 1280 px, 640 px (200 % zoom of a 1280 px window) and 320 px (400 % zoom), and with the WCAG text spacing values at each width.
- An automated scan with axe-core 4.7.2 (WCAG 2.0, 2.1 and 2.2 Level A and AA rules) on every page above, and in all twelve optional styles.
- Measurements of text, field-edge and focus-ring contrast in all twelve styles, and of target sizes.
- A keyboard walk of every page, menu, popup and dialog: each stop, its focus ring, whether anything covered it, Escape, the arrow keys, and where focus went.
- The flows that ask for data (New dashboard, Copy, widget settings), checked for anything asked for twice.
- Checks inside Jira on a development site after deploying this build: the focus rings fixed above, focus on a dashboard’s name, the More actions menu keys, the field edges, and the ways into the Advanced pages.
- A review of the code, with a test for each fix (3768 tests pass).
Not tested
- No screen reader (NVDA, JAWS, VoiceOver or TalkBack) has been used on any part of SmartDash.
- Only Chrome was used; Firefox, Safari and speech input were not tested.
- Most checks ran in the test setup, not inside Jira. Jira’s own frame and dialogs around SmartDash were not part of it; inside Jira only the items in method 7 were checked, in one style.
- The Switch chart and Size menus are covered by tests on the code; they were not opened on screen.
Scope: everything SmartDash draws. Jira’s page chrome, navigation, sign-in and the frames that host SmartDash are provided by Atlassian and are outside SmartDash’s control.
Terms
- Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: some functionality of the product does not meet the criterion. In this report it is also used where only part of the product was checked; the remarks say which part.
- Does Not Support: the majority of product functionality does not meet the criterion.
- Not Applicable: the criterion is not relevant to the product.
- Not Evaluated: the product has not been evaluated against the criterion.
In the remarks, “Advanced pages” means My view, SmartDash dashboards, the settings page and the AI box.
Table 1: Success criteria, Level A
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Charts with clickable parts are a group with a name that says what the chart shows, and each chart also has a data table hidden from sight but available to assistive technology. The loading mark and decorative icons are hidden from assistive technology. An automated scan (axe-core) found no problem on every widget, every widget's settings, My view, All dashboards, New dashboard, a SmartDash dashboard and the settings page, in all twelve styles. No screen reader has been used to hear these alternatives. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | SmartDash contains no audio or video content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No audio or video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No audio or video content. |
| 1.3.1 Info and Relationships | Partially Supports | List, table and pivot widgets are real tables with header cells. Form fields have bound labels, the AI box has a label, the project picker is a combo box with a list, and settings sections and dashboard lists are tab lists with tab panels. The automated scan found no structure problem on any page tested. Not confirmed: heading structure checked by a person, and how a screen reader reads the tables. |
| 1.3.2 Meaningful Sequence | Partially Supports | On every page tested the reading and Tab order follow the visual order. On SmartDash dashboards (Advanced) the built-in layouts place widgets in their saved order. Not checked: a dashboard arranged by hand, where widgets can sit in places that may not match their order in the page. |
| 1.3.3 Sensory Characteristics | Partially Supports | Most instructions name the control or field. A few short instructions also point by position, for example "No fields yet. Add one above." and "Answer the questions above first."; the thing to use is named, but its place is given only as above or below. No instruction relies on colour, shape or sound alone. |
| 1.4.1 Use of Color | Supports | A chart's values are also given as text in its legend table, its value card and its hidden data table; alert labels always carry words; goal, average and trend lines differ by dash pattern; a chosen option has a border and heavier text, not only a colour; late and at-risk items in My view say so in words. Checked on screen in the local test rig on every widget and Advanced page. |
| 1.4.2 Audio Control | Not Applicable | No audio plays. |
| 2.1.1 Keyboard | Partially Supports | Walked with the keyboard on every widget, every widget's settings and every Advanced page (My view with its first-time questions, All dashboards, New dashboard, a SmartDash dashboard, the settings page and the AI box). Fixed during this review (commit bc125f1): the Switch chart and Size menus on SmartWids were drawn at the end of the page, so Tab from their button never reached the choices; every menu now moves focus to its first item and takes the arrow keys. Widgets on SmartDash dashboards move and resize with the arrow keys or buttons. Seen inside Jira: the More actions menu by keyboard. The Switch chart and Size menus are covered by tests, not opened on screen. Not reachable by keyboard: the number of stays in the Time in Status widget's Per status bars, which is only in a hover tooltip (see 1.4.13). |
| 2.1.2 No Keyboard Trap | Supports | No trap was found on any page tested: focus moved through and out of every widget, menu, popup and dialog with Tab, and Escape closed each popup and menu. Menus now also close on Tab (commit 61f7328). Seen inside Jira on a SmartDash dashboard's More actions menu. |
| 2.1.4 Character Key Shortcuts | Not Applicable | SmartDash defines no single-character shortcuts. The keys it handles are Tab, Enter, Space, Escape, Home, End and the arrow keys. |
| 2.2.1 Timing Adjustable | Supports | SmartDash sets no time limit of its own; sign-in and sessions belong to Jira. Short confirmations ("Saved", "Up to date", "Copied") stay until the next action. |
| 2.2.2 Pause, Stop, Hide | Supports | Auto refresh is off unless the person who sets up the widget turns it on, and it reads again only while the widget is on screen and the tab is showing. A "Pause updates" button on My view and SmartDash dashboards, and "Pause auto refresh" in a widget's menu, stop everything that updates by itself; the browser remembers the choice. Blinks stop after five runs and the highlight pulse after four. All animations stop when the system asks for reduced motion. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing flashes more than three times a second. The fastest repeating effect is a once-a-second blink; the optional number blink runs once every 1.2 seconds. All of them stop under the reduced-motion setting. |
| 2.4.1 Bypass Blocks | Not Applicable | SmartDash is a set of widgets and pages embedded in Jira; Jira supplies the page navigation and its skip links. Each SmartDash widget is a single region. |
| 2.4.2 Page Titled | Supports | SmartDash's documents are titled "SmartDash". The page title that people see in the browser is set by Jira from the dashboard or app page. |
| 2.4.3 Focus Order | Supports | On every page tested the Tab order follows the visual order. Fixed during this review: focus now moves into a menu when it opens and back to its button when it closes (commit bc125f1); a dashboard opened inside the app puts focus on its name instead of nowhere (commits bc125f1, 61f7328). Settings and template dialogs keep focus inside while open. Seen inside Jira: focus on a dashboard's name after opening it from All dashboards, and back on the More actions button after Escape. |
| 2.4.4 Link Purpose (In Context) | Supports | Links are work-item keys beside their summary, counts named for what they open (for example "6 work items found. Open the search in Jira"), and named buttons. Checked on every page tested; each link's name was read from the page. |
| 2.5.1 Pointer Gestures | Supports | No function needs a multipoint or path-based gesture. Moving or resizing a widget by dragging depends only on where it is dropped, and the arrow keys and move buttons do the same. |
| 2.5.2 Pointer Cancellation | Supports | Actions run on click (the up event). "Clear all" in the project picker, closing a dialog by its backdrop and closing the AI box by clicking outside act on release. Dragging a widget starts on press and finishes on release, as dragging must. |
| 2.5.3 Label in Name | Partially Supports | Controls with visible text use that text as their name or start with it, for example "Remove" buttons named "Remove column ...". Symbol-only controls have a written name. No mismatch was found in the controls read during the keyboard walk; speech input was not used. |
| 2.5.4 Motion Actuation | Not Applicable | No motion- or device-sensor-based input. |
| 3.1.1 Language of Page | Supports | Every SmartDash document declares its language as English. |
| 3.2.1 On Focus | Supports | Receiving focus does not change the context. On focus the project picker opens its list, a chart part shows its value and read-only address fields select their text. None of these moves focus or opens a new page. Checked during the keyboard walk. |
| 3.2.2 On Input | Supports | In settings, changes only update a preview until Save. Choosing a role, release or project on My view redraws that page's answers in place and says so; the Filters widget updates the widgets that follow it only when Search is pressed, or as the person who set it up chose. Nothing opens a new page or moves focus on input. Checked during the keyboard walk. |
| 3.2.6 Consistent Help | Not Applicable | SmartDash screens offer no help mechanism of their own (contact, chat or help link). Help is on the Limbus Lab website. |
| 3.3.1 Error Identification | Supports | Errors are described in text next to what caused them, for example "Choose at least one project to start." or a limit that must be a number above 0, and the field points to its message. Error messages are marked as alerts. Not heard with a screen reader. |
| 3.3.2 Labels or Instructions | Supports | Every field on every page tested has a visible label or a visible prompt and a name read from the page: settings fields, the project picker, the role and release lists, the ask box on New dashboard, the AI box, the dashboard search and the Filters widget's fields. |
| 3.3.7 Redundant Entry | Supports | Checked by walking the flows that ask for information in steps. New dashboard from My view carries over the role and the projects already chosen there; the ask on New dashboard is kept when the plan is shown and changed; Copy a dashboard asks for one link; widget settings keep every tab's choices until Save. No flow asks for the same information twice. |
| 4.1.2 Name, Role, Value | Supports | Fixed during this review (commit bc125f1): the switches on the settings page had no on/off state while their value was loading; menus now behave as menus (focus inside, arrow keys); the widget options button no longer claims a popup menu. Charts with clickable parts are labelled groups, the project picker is a combo box with its expanded state and active option, tab lists use tab roles, and every button has a name. The automated scan found no problem on any page tested. No screen reader was used. |
Table 2: Success criteria, Level AA
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No audio or video content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No audio or video content. |
| 1.3.4 Orientation | Supports | No orientation lock and no orientation-specific styling; widgets and pages work in either orientation. |
| 1.3.5 Identify Input Purpose | Not Applicable | No field collects information about the user. |
| 1.4.3 Contrast (Minimum) | Supports | Scanned in all twelve styles on My view, All dashboards, New dashboard, every widget and the Chart settings, and in Jira's light and dark look on the widgets. Fixed during this review (commits 267053b, c8f44d0): in the Brutal, Soft and Plush styles the accent used as text on the page (New dashboard, Choose what shows, Save as a dashboard, work item keys) was 2.8 to 3.9:1 and is now 4.6:1 or more; in Soft, late and at-risk text was 3.7 and 4.2:1 and is now 4.6:1. After the fixes the scan found no contrast failure. |
| 1.4.4 Resize Text | Supports | Tested at 640 px width, which is 200 % zoom of a 1280 px window, on every widget, every widget's settings and every Advanced page: no text was cut off, overlapped or lost, and no page scrolled sideways. Text sizes follow browser zoom. |
| 1.4.5 Images of Text | Supports | All text is rendered text. The only image with letters is the SmartDash mark, which is a logo. A chart saved as a picture is a file the person chose to make. |
| 1.4.10 Reflow | Supports | Tested at 320 px width (400 % zoom) on every widget, every widget's settings and every Advanced page. Fixed during this review (commit bc125f1): the incident view of My view scrolled sideways because its role list did not wrap. After the fix no page scrolls sideways; List and table widgets scroll sideways inside their own box, as data tables may. |
| 1.4.11 Non-text Contrast | Supports | Measured: focus rings, field edges and control edges in all twelve styles. Fixed during this review: the focus ring of the current tab and of a project tag's × was 1:1 (commit bc125f1); field edges were 1.1 to 2.2:1 in five styles and on the role list, the first question box, the ask box, the open AI box and the Calendar's View list, and are now 3:1 or more (commits 267053b, c8f44d0). Chart colours are told apart by colour only, but every value is also given as text in the legend table, the value card and the hidden data table, so the colours are not needed to understand the chart. |
| 1.4.12 Text Spacing | Partially Supports | Tested with the WCAG values (line height 1.5, paragraph spacing 2, letter spacing 0.12, word spacing 0.16) on every widget, every widget's settings and every Advanced page at 1280, 640 and 320 px. Fixed during this review (commit bc125f1): work item names in My view and project names in the project picker were cut with "…"; they now wrap. Still open: chart legend names in a narrow chart end in "…" with these values; the full name is in the value card, the hidden data table and the CSV download. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Chart value cards appear on hover and on keyboard focus, stay while the pointer is on the part or on the card, and Escape closes them. In the Time in Status widget's Per status bars, the number of stays is only in the row's browser tooltip, which a keyboard cannot open; the time and the number of work items are shown as text. |
| 2.4.5 Multiple Ways | Supports | The Advanced pages can be reached from Jira's Apps menu and its sidebar (My Dashboard, SmartDash settings), from SmartDash's own tab bar on every page, and each SmartDash dashboard also from All dashboards with its search, from its own address (the Address for a browser tab button) and through SmartDash's Rovo. Seen inside Jira: the sidebar entry, the tab bar and All dashboards. |
| 2.4.6 Headings and Labels | Supports | Each Advanced page has one main heading (a dashboard's name, "SmartDash settings"); widget titles, settings sections and field labels say what they hold. Read from every page tested. |
| 2.4.7 Focus Visible | Supports | Focus was visible on every stop of the keyboard walk on every page tested. Fixed during this review (commit bc125f1): the focus ring of the current page's tab and of the × on a project tag could not be seen (1:1). Seen inside Jira after the fix. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | At every Tab stop on every page tested, at 1280, 640 and 320 px, the focused control was checked for anything drawn over it. Fixed during this review (commit bc125f1): for up to 10 seconds after a dashboard opens, the "Preparing your SmartDash…" overlay covered widgets that Tab could still reach; they are now out of the Tab order until it lifts. In the settings pop-up at 640 px a tall search box can be partly under the Cancel and Save bar, never fully hidden. |
| 2.5.7 Dragging Movements | Supports | On SmartDash dashboards (Advanced) a widget can be dragged, moved with the arrow keys on its move handle, or moved and resized with buttons that the move handle opens, so no dragging is needed. Field lists in settings have Up and Down buttons. |
| 2.5.8 Target Size (Minimum) | Supports | Measured by the automated scan on every page tested. Fixed during this review (commit bc125f1): the work item count link in the Filters widget was 20 by 13 px and is now at least 24 px. Smaller targets (list key links, line points, pie slices) are spaced at least 24 px apart. |
| 3.1.2 Language of Parts | Supports | All interface text is English. Names and values from Jira are shown as entered. |
| 3.2.3 Consistent Navigation | Supports | On the Advanced pages one tab bar is drawn by the same component on every page, in the same order. Seen on every Advanced page tested. |
| 3.2.4 Consistent Identification | Supports | Every widget uses the same frame, menu and settings dialog, with the same names ("Save", "Cancel", "Remove", "Delete"). |
| 3.3.3 Error Suggestion | Supports | Error messages say how to correct the input, for example "Choose at least one project to start." and "The first number must be below the second.". |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Deleting a SmartDash dashboard, deleting a template and removing a widget each ask first. Fixed during this review (commits ebc8614, 4d2f042): an Enter held down on Delete could also press "Yes, delete this dashboard"; a repeated key press is now ignored there. Changes on a dashboard stay unsaved until Save, and a new built dashboard can be undone. SmartDash never changes work items in Jira. |
| 3.3.8 Accessible Authentication (Minimum) | Not Applicable | SmartDash has no sign-in step; people are signed in by Atlassian. |
| 4.1.3 Status Messages | Partially Supports | Results, loading ("Preparing your SmartDash…") and errors are marked as status or alert messages, for example on My view, the Calendar and the dashboard page. Not heard with a screen reader. |
Table 3: Success criteria, Level AAA
Not evaluated.
Summary of ratings
| Conformance level | Level A (31 criteria) | Level AA (24 criteria) |
|---|---|---|
| Supports | 17 | 17 |
| Partially Supports | 6 | 3 |
| Does Not Support | 0 | 0 |
| Not Applicable | 8 | 4 |
| Not Evaluated | 0 | 0 |
Legal disclaimer: this report describes the build named above as reviewed on the report date. It is a self-assessment; no third-party audit and no screen-reader testing has been performed. The testing is described under evaluation methods; everything else rests on a review of the code.
AI
The company rules are in the AI Usage Policy. Only the Advanced edition uses AI. The Standard edition (the five widgets for Jira’s own dashboards) uses no AI or machine-learning model and makes no AI call.
The model and where it runs
SmartDash Advanced uses a Claude model hosted by Atlassian, called through Forge LLM, Atlassian’s AI service for Forge apps. It runs within Atlassian, under Atlassian’s terms for Forge. SmartDash sends nothing to any other AI provider, holds no AI key, and declares no outside address.
When it is used
Only when a person asks for it:
- to plan a dashboard from the words they type,
- to change a widget in words, when SmartDash’s own fixed rules cannot read the request,
- to change their My view page in words.
Nothing is sent to the model in the background.
What it is sent
| Sent | Never sent |
|---|---|
| The words the person typed; names from the site: project keys and kinds, whether a sprint is running, issue type, field, priority, status and SLA names, and the story points field name; and, for a change, the title and type of the widget being changed | Work items, their summaries, descriptions, comments or field values; anyone’s SmartDashes; secrets |
What it can and cannot do
- It only answers with text. SmartDash reads that text with its own fixed rules and checks it against fixed lists before anything changes. Anything outside those lists is dropped.
- It cannot read Jira. It has no access to work items or to anyone’s dashboards.
- It cannot change Jira. It cannot create, edit or delete work items, and cannot change anyone else’s dashboards. What it proposes is shown to the person to confirm, adjust or undo.
- Numbers come from Jira, not from the model. Every count and chart is read from Jira, as the viewer.
Limits and control
AI help is limited to 20 requests per person per hour and 400 per site per day. Above a limit, SmartDash reads the request with its built-in rules instead, or says that AI help has reached its limit. A Jira site admin can turn AI help off for the whole site in SmartDash’s settings. With it off, no request is sent to the model; widgets, dashboards and pages keep working without it.
Rovo
In Advanced, SmartDash also adds an agent to Rovo, Atlassian’s own AI. When a person asks Rovo about SmartDash, SmartDash answers as that person with dashboard titles, widget titles, counts and chart labels they can already see, never the rows of work items. Rovo actions are limited to 30 per person and 300 per site per hour. What Rovo does with the answer is covered by Atlassian’s terms.