Check these points before you install SmartDash: what your Jira site needs, which edition does what, the permissions Jira asks a site admin to approve, and the things SmartDash never does.
What you need
- Jira Cloud or Jira Service Management Cloud. SmartDash is an Atlassian Forge app for Jira Cloud. It is installed from the Atlassian Marketplace.
- A Jira site admin to install it. Only a site admin can install an app and approve its permissions. After that, anyone who can open a Jira dashboard can add SmartDash widgets to dashboards they may edit.
- A browser that Jira Cloud supports. SmartDash runs inside Jira pages, so it works where Jira works.
- Projects with work in them. Every widget reads Jira as the person looking, so each person sees the work items Jira already lets them see.
You do not need to know Jira Query Language (JQL). Every widget can pick projects or a saved filter instead.
Which edition does what
Standard and Advanced are one app. Your edition decides what shows.
| Edition | What you get |
|---|---|
| Standard | Five widgets for Jira's own dashboards, classic and new: Filters, Chart, List, Time in Status and Calendar. A settings page for Jira admins, with Where used, Site settings and Migration. No AI. |
| Advanced | Everything in Standard, plus SmartDash dashboards made of SmartWids, My view pages for 11 roles, sprint burndown and burnup, AI help hosted by Atlassian, and Rovo. |
On Standard, anything that is Advanced only says "This is part of SmartDash Advanced. Ask your Jira admin."
What SmartDash asks for
When a site admin installs SmartDash, Jira asks them to approve 17 permissions (scopes). SmartDash uses no others.
| Permission | In plain words |
|---|---|
read:jira-work | Read the work items a search finds, and the projects, fields, statuses, work types and priorities. |
read:jira-user | Read display names, for sharing and "shared by" names. |
read:group:jira | Find groups to share with, and check which groups a person is in. |
storage:app | Keep dashboard setups, settings and counts in the app's own storage on Atlassian. |
read:dashboard:jira | Read a classic Jira dashboard, for Migration and Where used. |
write:dashboard:jira | Make a copy of a classic dashboard (Migration), or a new private dashboard for the person asking Rovo. |
write:dashboard.property:jira | Save the widget settings on the dashboard SmartDash has just made. |
read:project:jira | Read project details that Jira sends back when it creates a dashboard. |
read:project-role:jira | Read project roles in that same answer. |
read:user:jira | Read the owner of that dashboard. |
read:application-role:jira | Read the product access in that same answer. |
read:avatar:jira | Read avatars in that same answer. |
read:issue-type-hierarchy:jira | Read the work type levels in that same answer. |
read:issue-type:jira | Read work types in that same answer. |
read:project-category:jira | Read project categories in that same answer. |
read:project-version:jira | Read versions in that same answer. |
read:project.component:jira | Read components in that same answer. |
The dashboard permissions are used only in two cases, both started by a person and always as that person: Migration's copy of a classic dashboard, and Rovo putting a SmartDash's widgets on a new private Jira dashboard. An original dashboard is never changed. For more, see Permissions and data for admins.
What SmartDash does not do
- It does not change work items. It has no permission to create, edit, transition, comment on or delete work items, projects, fields, users or groups.
- It does not keep work items on a server. It stores setups. Numbers are read from Jira each time they are shown.
- It sends nothing outside Atlassian. It runs on Atlassian Forge, lists no outside address and is eligible for Runs on Atlassian.
- It does not show more than Jira allows, unless an admin turns on Share project data for one SmartDash and one project. See Share a SmartDash.
Related pages
Need help with SmartDash? Contact us