Questions to ask any
Jira dashboard app
49 plain questions to put to the vendor of an app that adds dashboards, charts and reports to Jira Cloud, in 6 groups. Under each question is the one-line answer for SmartDash, with a link to the page that explains it.
Reads Jira as the person looking. SmartDash runs entirely on Atlassian Forge, so question 1 on the list has a short answer.
Data and security
Where your Jira data goes, what the app keeps, and how security problems are handled.
| Question to ask | What SmartDash does |
|---|---|
| 1.Does your Jira data pass through a server run by the app’s vendor? | No. SmartDash runs entirely on Atlassian Forge and lists no outside address, so nothing it handles leaves Atlassian. It is eligible for Runs on Atlassian. Architecture and data flow |
| 2.Does the app keep a copy of your work items? | No. SmartDash stores dashboard setups and settings, never work item summaries, descriptions, comments or field values. Numbers and work items are read from Jira each time they are shown. Data and privacy |
| 3.What exactly does it store, and where? | A widget’s settings are saved by Jira with its dashboard, like any gadget’s settings. Everything else, such as SmartDash dashboard setups, sharing, site settings and personal layouts, is kept in Forge hosted storage provisioned for your site. Data retention and deletion |
| 4.Is stored data encrypted at rest? | SmartDash stores data only in Forge hosted storage and in Jira. Atlassian encrypts Forge hosted storage on disk and scopes it per installation; the algorithm and keys are operated by Atlassian. Encryption at rest |
| 5.What does the app leave in a person’s browser? | The last result of each widget that person opened, so a dashboard shows at once. It is never shown to anyone else, a result older than 48 hours is never shown and is deleted, and at most 200 are kept. In your browser |
| 6.Who are the app’s subprocessors? | Atlassian only, for Forge hosting, storage and logs. SmartDash declares no other outside service. Subprocessors |
| 7.What goes into the app’s logs, and who reads them? | A line is written when something fails, to Atlassian’s Forge logging service. SmartDash does not deliberately log work item text, field values or the words people type. Site admins can switch the developer’s access to their site’s logs off. Data logging and retention |
| 8.Does the app send usage analytics or telemetry anywhere? | No. SmartDash sends no usage analytics or telemetry to Limbus Lab or anyone else. The open counts a SmartDash shows its owner stay in Forge storage, inside the app. Our position on logs |
| 9.What happens to the app’s data when you uninstall it? | Atlassian removes the app’s Forge storage under its platform lifecycle; Atlassian documents a 28-day retention after uninstall. Uninstalling cannot reach a browser, so browser copies stay until they expire or the site data is cleared. Deleting data |
| 10.Where is the data held, and does it follow data residency? | Forge hosted storage is held in the location of your Jira site and moves with it when an admin migrates the product, according to Atlassian’s Forge documentation. SmartDash sends no data to another location. Data residency |
| 11.How are security reports and incidents handled? | Reports are acknowledged within 3 business days, with fix targets by severity (7 days for critical, 30 for high, 90 for medium). Customers whose data is involved are told no later than 72 hours after a breach is confirmed. Security and incident response |
| 12.Is ticket text made safe before it is shown or exported? | Yes. Descriptions and comments opened from SmartDash are cleaned of scripts, styles, forms and frames, text people type is shown as text, and CSV cells that look like a spreadsheet formula are made harmless. Built-in safeguards |
Permissions and access
Whose access decides what a person sees, what the app may change in Jira, and who can share what.
| Question to ask | What SmartDash does |
|---|---|
| 13.Whose Jira permissions decide what a viewer sees? | The viewer’s. Every widget and page reads Jira as the person looking at it, so a viewer with access to fewer projects sees fewer work items. Read live, as the viewer |
| 14.Can a viewer ever see work items that Jira hides from them? | Only through Share project data in Advanced, which a Jira admin or an admin of that project turns on, on purpose, for one SmartDash and one project. It stops if the approver is not checked again within 30 days, and is dropped if they are no longer an admin. Share project data |
| 15.Which Jira permissions (scopes) does the app ask for, and why? | Read work, read users and groups, app storage, read and write dashboards, and read-only project details. Each is listed with its use, and an update that adds a permission asks a site admin to approve it. Permissions and data for admins |
| 16.Can the app create, edit or delete work items? | No. SmartDash has no permission to create, edit, transition, comment on or delete work items, projects, fields, users or groups. Jira permissions |
| 17.When, if ever, does the app change anything in Jira? | In one case only, started by a person and done as that person: an admin’s copy of a classic dashboard on the Migration tab. An original dashboard is never changed. Built-in safeguards |
| 18.Who can share a dashboard, and with whom? | Only its owner, in Advanced: with everyone on the site, or with up to 500 people, 100 groups and 25 projects. A Jira admin can turn sharing off for the site. Share a SmartDash |
| 19.What does a person see when a dashboard is not shared with them? | The same “not found” message as for a dashboard that does not exist, so SmartDash does not reveal that it exists. Who can see what |
| 20.Are admin settings protected on the server, or only hidden in the page? | On the server. Only Jira site admins can open the settings page, and every change is checked again by SmartDash’s functions, so a non-admin cannot change a setting by any other route. Global settings |
| 21.Does the app show people’s email addresses? | No. It looks up display names for sharing and “shared by” names. Email addresses are not shown. Jira permissions |
Accuracy of the numbers
Where the counts come from, what happens on a large site, and whether the app tells you when it stops.
| Question to ask | What SmartDash does |
|---|---|
| 22.Where do the counts come from, and can you check them against Jira? | From Jira’s own searches, using each widget’s search exactly as written. Open in filter opens the same search in Jira, so you can compare. Counting and scale |
| 23.What happens on a site with a very large number of work items? | Numbers are counted exactly up to 10,000 work items. Above that, Jira’s own estimate is shown, and the widget says it is an estimate. Limits at a glance |
| 24.Does the list behind a bar match the number on the bar? | Yes. The drill-down uses the same search as the chart, so the numbers match. At most 200 work items are listed, and the page says so when there are more. Drill into a bar or slice |
| 25.Why can bars add up to more or less than the total? | A work item with no value in the grouped field is in no bar, and one with several values, such as several labels, is counted in each bar but once in the total. A note on the chart says so. Why a number may differ |
| 26.What does a calendar do when a month holds thousands of work items? | A Calendar layer with more than 2,000 work items uses Jira’s own count for each day instead of stopping short. That count can be a little off, and the Calendar says so. Calendar limits |
| 27.Does the app tell you when it hits a limit, or cut off quietly? | It tells you. Each limit has its own message on the widget, such as “First 500 work items” on Time in Status or “N segments show only the first 2,000 work items” on a chart. Limits at a glance |
| 28.How are dates and time zones handled in counts? | Dates are read by day. A count near the edge of a period can land in the neighbouring period for people far from the site’s time zone. Why a number may differ |
Jira dashboards, old and new
What works on Jira’s classic dashboards and on its new dashboards, and what Jira itself does not let any app do.
| Question to ask | What SmartDash does |
|---|---|
| 29.Does it work on both classic and new Jira dashboards? | Yes. The five widgets work as gadgets on classic dashboards and as widgets on Jira’s new dashboards, with the same settings in each place. This is in both editions. The five widgets |
| 30.Which widgets and chart types are included? | Filters, Chart, List, Time in Status and Calendar. The Chart draws pie, bar, grouped and stacked bar, line, funnel, table and tiles, with goal lines, target bands and colour rules. The Chart widget |
| 31.Does it follow the filter row of a new Jira dashboard? | Yes, when a widget’s source is Dashboard. It reads the space, status, assignee, work type, priority, label and other fields by name. A filter it cannot read is named on the widget, never guessed. The filter row of a new dashboard |
| 32.Can it copy an existing classic dashboard that uses its widgets? | Yes. A Jira site admin’s Migration tab makes a copy with SmartDash widgets in place of the gadgets it can replace. The original is not changed, and the copy keeps its layout and searches. Migration |
| 33.Can the app create a new-style Jira dashboard for you? | No. Jira does not let any app create a new-style dashboard or add widgets to one. You create it in Jira and add the SmartDash widgets yourself. New Jira dashboards |
| 34.Can people export what they see? | A List exports as CSV, a chart’s numbers can be downloaded as CSV, and a SmartDash setup exports as a file with no work item data. A Jira admin can take export choices out of the menus. Download and export |
| 35.Does it follow Jira’s light and dark themes? | Yes. Widgets ask Jira which theme it is in and change when the person changes theme. Admins can set theme colours, and SmartDash warns when text would be hard to read. Accessibility |
| 36.Does a widget keep reading Jira when nobody is looking at it? | No. A widget reads Jira only while it is on screen, and a hidden tab or locked screen refreshes nothing. Refresh and wallboard |
| 37.Can a dashboard run on a team screen as a wallboard? | In Advanced, yes. A SmartDash can fill the screen and keep refreshing while the screen is on, never faster than every 30 seconds. The viewer must be signed in and the SmartDash shared with them. Show a SmartDash as a wallboard |
Jira Service Management
What a service desk, incident or change team gets from the same app.
| Question to ask | What SmartDash does |
|---|---|
| 38.Does it read Jira Service Management projects? | Yes. Widgets read service projects like any other, as the person looking. FAQ |
| 39.Can it show SLAs? | Yes. A Calendar layer can use the SLAs a service project runs, shown as met, not met and running. Calendar |
| 40.Are there pages for service roles? | In Advanced, My view has five: service desk agent, incident manager, problem manager, change manager, and service owner or support lead. Each opens on the questions that role asks every day. My view |
| 41.How current are breach warnings? | On the incident manager page, what is on fire and what is about to breach update every minute while they are on screen. A project with no SLAs does not get the breach question. The roles and their questions |
Admin, editions and support
Setup, editions, what happens to dashboards over time, and how the app is checked and supported.
| Question to ask | What SmartDash does |
|---|---|
| 42.What is the difference between the editions? | Standard gives five widgets for classic and new Jira dashboards. Advanced adds SmartDash dashboards, My view for 11 roles, and sprint burndown and burnup. They are one app; your edition decides what shows. Overview |
| 43.Do people need to know JQL? | No. A widget’s work items can come from a Filters widget, projects picked from a list, or a saved filter. JQL is there for those who want it, up to 2,000 characters. Choose where the work items come from |
| 44.What happens to a dashboard when its owner leaves? | It keeps working for the people it is shared with, but nobody can change it until a Jira site admin hands it to a new owner from the settings page. When an owner has left |
| 45.Does the app ever delete dashboards on its own? | No. A site admin can choose to archive dashboards nobody has opened for a while. Archived means hidden, not deleted, and an admin can restore them. Archive and restore |
| 46.How is each release checked? | Each change comes with over 3,000 automated tests and is tried on a staging site first, in both editions. |
| 47.Where can you see the service status and past incidents? | On the public SmartDash status page, which shows Atlassian’s Jira and Forge status and the SmartDash incident list. Incidents follow a written response plan. SmartDash status |
| 48.What has been checked for accessibility? | Keyboard use, visible focus, reduced motion, tables with headings and colour that is not the only signal are built in. A full WCAG 2.2 evaluation has not been done yet, and the page says what has not been checked. Accessibility |
| 49.How do you get a price or a demo? | Prices are not published on this site. Get in touch and we will answer, and show SmartDash on your own Jira site. Contact us |
Go further
Want to raise a ticket? Click here (opens in a new tab)
SmartDash demos
We show SmartDash on your own Jira site. Write to us to arrange one.