/ Products · Glanceable Boards

Glanceable Boards user guide

A visual card board over the Jira issues you already have. This page is the documentation URL for the Marketplace listing.

Related: Product page · Privacy policy · Licence

Who this is for

• Marketing and creative teams who were put on Jira and need a board they can read at a glance
• Project members who already have access to the Jira project — the app uses your Jira permissions
• Project administrators who set board scope, list-to-status mapping and field visibility

Install

1. Open Glanceable Boards on the Atlassian Marketplace and install it on your Jira Cloud site.
2. A site admin must approve the install. The app asks for read and write on Jira work, read on Jira users, and Forge app storage.
3. Open a software or business project. The project navigation includes a Glanceable Boards tab.

The app does not appear on Jira Service Management projects.

Create a board

1. Open the Glanceable Boards tab on the project.
2. Choose a template: Blank, Marketing campaign, or Content calendar.
3. Name the board. The template supplies list names and a label palette.

The board shows issues that match its JQL scope. An issue in scope with no placement lands in the landing list. You can change the scope later in board settings.

Work with cards

Cards are Jira issues. Adding a card creates an issue with a summary. The tile shows cover, title, label chips, due date, assignee, checklist progress and attachment count. Issue type, priority, points, sprint, epic and status stay hidden unless you turn them on in field visibility.

• Drag a card inside a list to change rank.
• Drag a card to another list to move it. If that list maps to a Jira status and the transition is allowed, Jira updates the status. If the transition is refused, the card snaps back with the reason.
• Set a picture cover from an attachment, or a colour cover, from the card or the card back.

The card back

Click a card to open it. You can edit the title and description, set labels and due date, assign someone, tick checklist items, upload attachments, and add a Jira comment. The overflow menu archives the card or opens the issue in Jira.

Comments, mentions, assignees and attachments go through Jira as you. The app does not keep a second copy.

Lists and status

Lists belong to the board. Anyone who can use the board can add, rename and reorder them — you do not need to be a Jira workflow admin. A list can optionally map to a Jira status. Mapping is how a card move becomes a Jira transition.

Board settings

Administrators can change the board name, JQL scope, theme (cover size and density), visible fields, label palette, list-to-status mapping and the landing list.

Archive

Archive hides a card on this board. The Jira issue stays. You can send an archived card back to the board later. Uninstalling the app does not delete your Jira issues.

FAQ

Does this replace Jira boards?

No. It is a project-page view over the issues you already have. Native Jira boards, filters and reporting keep working.

Where is data stored?

Board settings in Atlassian Forge key-value storage. Optional background images in Forge Object Store. Per-card placement, cover, checklist and archive flags on your own Jira issues as issue properties. See the privacy policy.

Who can see an issue?

Whoever Jira already allows. The app calls Jira as the signed-in user and cannot show an issue Jira would hide.

How do I get support?

Email help@softwired.com.au with your Jira site URL.

Published by Softwired Digital Pty Ltd, Brisbane.