How to link and sync status where multiple smartsheet rows need to link to a single Jira ticket?

I have a sheet with stakeholder requirements for a software development project. The rows are the individual requirements. Our engineering teams are working in Jira so their work items are Jira tickets. I need to be able to sync the Jira ticket statuses to the relevant line item in Smartsheet.

The status sync works fine when it's a 1:1 relationship, one Jira ticket for one Smartsheet row. But there are cases where a single Jira ticket needs to map to multiple Smartsheet items. In this case, it is only syncing the status for the first instance of a ticket in the sheet. It does correctly turn the manually typed issue key into a link to the issue, but the status column doesn't fill in.

Is there a way to get it to properly link and sync when the same Jira ticket needs to link to multiple Smartsheet rows? Here's what it looks like in my test sheet.

Find more posts tagged with

Jira Connector

Sync

Accepted answers

Georgie

Hi @EGHW,

The Smartsheet Jira Connector supports a one-to-one mapping between Jira issues and Smartsheet rows. The Issue Key is the primary identifier for issues in Jira. If there are multiple instances of the same issue key in Jira, the Connector cannot uniquely map those to separate rows in Smartsheet.

Best practice is to have a unique issue key for each Jira issue, so that it can be mapped to the Issue Key column in Smartsheet. More information can be found here.

Hope that helps!

Georgie

All comments

Georgie

Hi @EGHW,

Best practice is to have a unique issue key for each Jira issue, so that it can be mapped to the Issue Key column in Smartsheet. More information can be found here.

Hope that helps!

Georgie

EGHW

Thanks, appreciate the answer. Having a unique Jira key for each Smartsheet row would result in a bunch of useless empty Jira tickets that do not logically map to the actual Smartsheet deliverable. I guess for this project I'll have to manually keep Smartsheet updated with Jira statuses.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.