Smartsheet for Jira: Tips for field mapping in your workflow

Applies to

  • Business
  • Enterprise
Smartsheet Advance Package


Who can use this capability

You must be a Sysadmin on Smartsheet and Jira to configure the connector. You must be a licensed Smartsheet user to create or edit a workflow. You'll also need a Jira account with access to your Jira project. 

When you use Smartsheet for Jira, field mapping and filters control what data is exchanged and how it moves between Jira and Smartsheet.

Field mapping

You map fields from Jira to columns in a sheet. Available Jira fields depend on what fields are available in the Jira project(s) you select for the workflow. You can also specify the direction that you want data to flow – from Smartsheet to Jira, from Jira to Smartsheet, or both directions.

Things to know about mapping 

  • Issue Key and Error Column are required; they will appear in your workflows field mappings by default. You cannot remove them from the workflow. If you delete one of these columns from your sheet, Jira will return an error code when you sync your data. (See Finding and Fixing Workflow Errors for more information.)
  • The Issue Key is the primary identifier for issues in JIRA. Without this required value, the Smartsheet for Jira Connector cannot write changes back to that Issue in Jira.
  • Certain fields from Jira will appear with only a unidirectional mapping option (Issue Key, Jira Link, Issue Link, Created Date, etc.). These fields are read-only from Jira and cannot be written to from Smartsheet. 
  • Fields must appear on the Create Issue screen in Jira to appear as options in the workflow wizard. More information on screens in Jira can be found in the Atlassian Documentation article on Defining a Screen.
  • You must always specify a Smartsheet column to map fields to. You can not leave the mapping blank.
  • When you create new columns in a workflow, the column type created in the sheet will vary depending on the field type being mapped (for example, a date value from Jira will be mapped to Date column). The workflow wizard will show the column type in the sheet in parentheses. 
  • The Reporter field in Jira will show as Reporter Email Address and Reporter Display Name options in the workflow wizard.
  • The Assignee field in Jira will show as Assignee and Assignee Display Name options in the workflow wizard.
  • To use the Assignee field in Jira with a Contact List column in Smartsheet, make sure the user’s email is the same in Smartsheet as the user's Jira login. (For more information about column types, see the Column Types article in the Help Center.)
  • If you build a workflow off an existing sheet, columns with matching field names will be mapped automatically in the workflow wizard. Those fields are: (Issue Type, Summary, Reporter Email Address, Description, Priority, Assignee)

Mapping Time to Resolution and First Response fields

Map Jira’s Time to Resolution and Time to First Response fields to leverage Service-Level Agreement (SLA) information in Smartsheet. Use this data to get a better picture on your SLA metrics.

Keep the following in mind when mapping these fields:

  • Both “Time to First Response” and “Time to Resolution” are broken into subcategories (such as Earliest Duration Goal, Earliest Duration, and Ongoing Duration Goal). Map each subcategory to a column in the sheet.
  • Data will from these fields be mapped to the sheet as an integer in minutes.
  • Mapping Goals (earliest, ongoing, and longest) allow you to sync the SLA’s you’ve set in Jira to take advantage of Smartsheet formulas and visualization features.
  • Time to Resolution’s Earliest Duration and Longest Duration will only have values when the Jira issue is resolved at least once.
  • Time to Resolution’s Ongoing Duration will have a value only while the issue is unresolved.