Design your workflow.
Keep Jira connected.

Build the board your work needs, from Kanban flow to story-mapping workshops. Set your own card details and rules, keep working changes on the board, and choose what reaches Jira.

In development. These capabilities describe the product we're building; the early demo covers a smaller subset.

Cadensight Kanban board with doing and done sections within a workflow stage, swimlanes, a work-in-progress limit and a visible team policy.
App screenshot · Example Kanban board · Sample data

One canvas for delivery and planning.

Show how work moves, make team agreements actionable, and carry workshop decisions into Jira when they're ready.

Cadensight Kanban board with doing and done sections within a workflow stage, swimlanes, a work-in-progress limit and a visible team policy.
App screenshot · Example Kanban board

Open-board design

Make the real workflow visible.

Design a board around how your team works, then choose how it maps to Jira. Separate doing from done within a status, give different kinds of work their own swimlanes, and keep policies beside the cards. Make agreed WIP limits enforceable where the team controls incoming work.

An ML2 Kanban example, with the working agreements in view.

Figma Jira-sync design over the real board. Three selected cards contain five changes to priority, estimates, assignee and release; one unchanged card is already in sync.
Figma sync design · Sample workshop changes

Board-owned data and Jira sync

Change your mind before you change Jira.

A workshop needs room for a second thought. Change estimates, reconsider priorities and move work between releases while those edits stay on the board. Undo a detour, review the final field changes, then send the agreed set to Jira together. Keep board-only notes and decisions out of that update.

Discuss, revise, then sync the decisions you keep.

An appointment-booking story map in Cadensight. Find time, Book visit and Manage columns cross two release slices; Confirm booking sits in Book visit and Release 1.
App screenshot · Illustrates planned Jira assignment

Workshop design and facilitation

Keep the journey in your release plan.

Map the customer journey together and find a first release that works from end to end. Create stories beneath the activities they support, then arrange the release slices. Configure a card's placement to assign its epic and sprint or release together, so the layout carries the plan's meaning into Jira.

One placement connects a story to its epic and release.

Review-handoff rule concept using Cadensight's visual and code editor styles. An unblocked-story condition leads to status, assignee and approver assignments.
Rule editor concept · Based on the app editor

Deeply customizable rules

Build the handoff into the move.

Turn a team's agreement into conditions and actions on cards, transitions and fields. For a review handoff, configure the transition to set the assignee and approver automatically when its conditions are met. Use the visual designer or edit the logic in code. Assigning an approver still leaves the approval to a person.

A review handoff with ownership already assigned.

Concept illustration of one team's board containing a Sprint risk level field and board-owned Risk and Experiment cards, with a separate board beside it.
Concept illustration · Board-owned data

Board-owned fields and cards

Add context without another Jira field.

Give your team a “Sprint risk level” field without adding a field to Jira's configuration. Keep Risk, Experiment or Decision cards on the board without introducing new Jira work-item types. The team gets the context it needs, while board-only data stays separate from the information maintained in Jira.

A risk scale for this board, without changing other teams' boards.

Figma card-designer example for APP-102, Reserve a slot. The layout and preview show assignee Alex Morgan, High priority, 5 story points and a blocked flag.
Figma design · Daily review example

Customizable card designer

See what needs attention on the card.

Make the card useful for the conversation in front of you. In a daily review, show the assignee, priority, estimate and blocked indicator so the team can identify the next action without opening every ticket. Choose the fields and indicators that matter to your team and keep the rest out of the way.

A daily review card that makes blockers and ownership visible.

Sample data throughout. Captions distinguish app screenshots, Figma designs and concepts. Select an image to explore it at full size.

From the canvas to Jira.

  1. 01

    Shape the canvas

    Arrange the board for the delivery flow or workshop your team needs.

  2. 02

    Give placement meaning

    Choose card details, fields and rules that connect the board's layout to the work.

  3. 03

    Work, review, sync

    Explore on the board, then review what goes to Jira and what stays here.

Explore a small part of the experience today.

Try the early product

Frequently asked questions.

We already have Jira and a whiteboard. Why add Cadensight?

Cadensight is for teams whose delivery workflow or planning workshops need more than their current setup comfortably expresses. It brings a flexible canvas, team-specific working data, and customizable cards and rules together with Jira. The value is a working surface shaped around your team's decisions, from daily flow to release planning.

Does Cadensight replace Jira or require us to move our work?

Cadensight works alongside Jira. Your Jira work items stay in Jira, while Cadensight gives your team another way to organize and work with them. Teams can also keep their own planning context on the board without turning all of it into shared Jira configuration.

Which Jira environment is the release being built for?

The planned release is for Jira Cloud, built on Atlassian Forge and hosted on Atlassian's infrastructure. You will not need to operate a separate Cadensight server. The early product preview is a separate environment and does not represent the release's hosting or security model.

How will we install Cadensight, and who needs to approve it?

We plan to distribute Cadensight through the Atlassian Marketplace. Your organization's authorized app administrator can review the requested permissions and approve installation through Atlassian's app management process. Cadensight is still in development; the Marketplace release is not available to install yet.

Will we need developers to set it up?

The board, card designer and visual rule designer are intended to let teams shape their setup without writing code. A code editor is available for more complex rule logic. Choose someone to own the team's working agreements and configuration; ordinary board use should not require everyone to become a tool specialist.

What will Cadensight cost?

Pricing and licensing are still being defined. We will publish them before the Marketplace release so you can assess the cost before installing. Joining the release waitlist is free and does not commit you to a purchase.

Will Cadensight Lab be able to see our Jira or board data?

Our commitment for the Forge release is that Cadensight Lab will not have access to your Jira or board data. Vendor-visible logs will contain general infrastructure information, with instance data excluded. The app itself will process the data needed to operate within the permissions approved for your installation.

What visibility will our enterprise administrators have?

We will provide enterprise administrators with detailed application logging and telemetry to support oversight and troubleshooting. That administrator visibility is separate from the general infrastructure logs available to Cadensight Lab. The release documentation will describe the available records, access controls and retention periods.

Will Cadensight have Atlassian trust badges?

We intend to qualify for Runs on Atlassian and pursue Atlassian's enterprise app assurance program. Cloud Fortified is being replaced by Atlassian Enterprise Certified. These are release goals, not badges Cadensight has already earned; our Marketplace listing will show the status achieved.

What about compliance, data residency and retention?

The release will use Atlassian Forge's platform protections. Cadensight's app-specific privacy, data residency, retention and deletion documentation is in progress and will be available before installation. We will distinguish the protections Atlassian provides from Cadensight's responsibilities and any independently verified certifications, so your team can complete its own review.

Make room for your team's way of working.

Get release updates and an invitation when Cadensight for Jira is ready to try.