Keep the tools your teams use
Your PMO’s sheet sits above the Jira work your teams already plan, connecting portfolio objectives to delivery evidence.
Planning & delivery intelligence
Capasight for Smartsheet and Jira
Your portfolio in Smartsheet. Your delivery in Jira. One shared picture.
Hosted Capasight connects your Smartsheet portfolio with the delivery work in Jira. PMOs and delivery leaders can inspect the same hierarchy, compare commitments with the work beneath them, and follow findings to a practical action.
- Application
- Hosted Capasight at app.capasight.co.uk
- Planning inputs
- Smartsheet rows, sizes, dates and Jira keys; Jira delivery work
- Connection
- Smartsheet service account or an Excel export
- Availability
- Hosted Capasight only; not Lite or marketplace apps
From a planning question to evidence.
Check the promise against the work
Compare the dates and sizes in Smartsheet with the Jira work beneath them to see where the two plans diverge.
Follow a finding to an action
See what needs attention and whether to review the portfolio date or the timing of the underlying Jira work.
The same plan. More evidence to act on.
Keep the planning view your teams use. Add the scope, date and capacity context behind the commitment.
Smartsheet · portfolio commitmentsThemes and indented initiatives, with sizes, dates and Jira keys.
Jira · delivery workLinked initiatives, features, epics and stories, with estimates, teams and sprints.
Capasight · one shared pictureInspect dates, scope, demand, capacity and actions across the joined levels.
The sheet’s indentation identifies its parent and child rows. Jira keys on each row identify the delivery work beneath it. Capasight uses those recorded relationships and shows what does not join; it changes neither source.
Data retention · same test-portfolio commitment
The Smartsheet portfolio
Data retention names the Jira work and promises 28 May 2027.
The same commitment in Capasight
The linked Jira work runs to 5 July 2027: a 38-day gap, with a suggested action.
Source-pack test portfolio, not customer data. Both views show the Data retention commitment; open either capture to inspect it at full size.
Explore the evidence, screen by screen
Expand a screen for its purpose and a test-portfolio example.
Follow the Data retention example into Jira
Smartsheet row 7 sits under the Customer and compliance theme. It names CCM-788 and CCM-798 and promises 28 May 2027. Jira initiative CCM-788 contains features CCM-806, CCM-807 and CCM-808, with epics and stories beneath them and work planned to 5 July 2027. The joined view exposes the 38-day gap; the suggested action is to review the portfolio date or bring the linked Jira work into earlier sprints.
Overview · one hierarchy across two tools
See the sheet’s Themes and initiatives alongside Jira’s Initiatives and Features. Each level shows lateness and demand against capacity, connecting the portfolio commitment with the delivery work behind it. All figures shown are from the test portfolio.
Dates · check the portfolio promise against delivery
Inspect the Smartsheet levels using the names your PMO recognises. In this test portfolio, 91% of the Smartsheet initiatives show a date problem when the Jira work beneath them is considered. This is an example finding, not a customer result.
Connection checks · see what does not join
Review Jira keys that cannot be found, rows linked to an item lower down an existing Jira chain, rows without Jira keys, and open Jira work that no sheet row claims. These checks make gaps in the joined picture visible before you rely on it.
Joined structure · inspect the links row by row
Follow each sheet row to the row it is indented beneath and the Jira items whose keys it records. Unrecognised Jira keys are marked on their row, so you can review the source data rather than accept a guessed relationship.
Levels and sizes · use your PMO’s planning language
Name each Smartsheet layer and give it its own t-shirt scale alongside the Jira levels. Inspect scope and demand in a consistent unit across the joined portfolio, while retaining the distinctions between levels.
Settings · choose the connection and review data handling
Connect through a service account with Viewer access, or upload an Excel export. Settings explains the inputs used, the joined structure and what Capasight retains. The API route requires Smartsheet Business or higher; Excel export works with any plan.
Pricing for Smartsheet + Jira.
Smartsheet + Jira · Hosted Capasight
Part of a hosted Capasight proposal.
Connect your Smartsheet portfolio to Jira delivery in hosted Capasight. Discuss the planning scope, connections and deployment requirements with us; no separate Smartsheet app rate is published.
This connection is not included in Capasight:Lite, the Azure DevOps extension or the monday.com app. Your Smartsheet and Jira subscriptions are separate; API access needs Smartsheet Business or higher, while any plan can use an Excel export.
Set up with the evidence you already keep.
Planning inputs, setup and access
Before you start
- Use hosted Capasight with the Jira connection for the delivery work you want to inspect.
- Prepare the portfolio sheet with parent and child rows, names, t-shirt sizes, dates, done status and the Jira keys the rows deliver through.
- For the API route, use a Smartsheet Business plan or higher and a service account with Viewer access to the sheet. Any plan can use an Excel export.
Connect, inspect and review
- Bring in the sheet. Connect the service account or upload File › Export › Microsoft Excel from Smartsheet.
- Check the joined structure. Review the hierarchy, missing Jira keys, links lower down an existing Jira chain, rows without keys and open Jira work no row claims.
- Name the layers. Use your PMO’s level names and confirm a size scale for each layer.
- Read the evidence. Inspect demand against capacity, dates, findings and actions across the joined levels.
How data is handled
Capasight reads the sheet when asked and changes neither source. An Excel upload is a snapshot, not an ongoing connection. Uploaded files are read and not kept.
Read the security detail for this application → · Hosted Capasight only.
Questions before you connect.
How does Capasight connect Smartsheet and Jira?
The sheet’s indentation identifies parent and child rows. Jira keys on each row identify the delivery items beneath it. Capasight uses those explicit relationships and shows what does not join.
Which Capasight application includes Smartsheet?
Smartsheet is supported in hosted Capasight. It is not in Capasight:Lite for Jira, the Azure DevOps extension or the monday.com app.
Do I need Smartsheet API access?
The API connection needs a Smartsheet Business plan or higher. An Excel export can be used from any Smartsheet plan.
When does Capasight read the sheet?
Capasight reads the sheet when asked; an Excel upload is a snapshot. It writes to neither Smartsheet nor Jira and does not replace Smartsheet’s Jira Connector.
What happens to an uploaded file and imported rows?
The uploaded file is read and not kept. Removing the connection removes its imported rows; those rows leave daily backups within 30 days.
What does Capasight retain from Smartsheet?
Only each row’s name, t-shirt size, dates, done status, position in the sheet and named Jira items are retained. Uploaded files are read and not kept. Removing the connection removes the imported rows; they leave daily backups within 30 days.
Bring your planning question.
Talk through the plan you need to inspect and the evidence available in your tools.