SpecSync Documentation
Jira
Jira
  • Introduction to SpecSync for Jira
  • Getting started
    • Getting started using SpecFlow
    • Getting started using Cucumber or other Gherkin-based BDD tool
  • Installation & Setup
    • Install as .NET tool
    • Install as .NET Console App
    • Install as native binaries for Linux or macOS
    • Install as Docker image
    • Setup and Configure
  • Features
    • Push features
      • Pushing scenario changes to Test Cases
      • Configuring the format of the synchronized test cases
      • Synchronizing Scenario Outlines
      • Update Test Case fields
      • Attach files to Test Cases using tags
      • Customization: Setting Test Case fields with default values
      • Customization: Update custom Test Case fields on push
      • Customization: Ignoring marked Test Case steps
      • Customization: Ignoring Test Case Tags
      • Customization: Ignore non-supported local tags
      • Customization: Mapping tags
      • Customization: Synchronizing scenarios from feature branches
      • Customization: Automatically link changed Test Cases
      • Customization: Synchronize linked artifact titles
      • Customization: Do not synchronize title
    • Pull features
      • Pulling Test Case changes to local scenarios
    • Common synchronization features
      • Configuration key
      • Remote scope
      • Linking Work Items using tags
      • Synchronizing Test Case hierarchies
      • Excluding scenarios from synchronization
      • Synchronization conflict resolution
    • Test result publishing features
      • Publishing test result files
    • General features
      • Jira authentication options
      • Configuration file
      • Hierarchical configuration files
      • Local test case conditions
      • Configuration wizards
      • SpecSync plugins
    • Customizations
    • Plugin list
  • Licensing
  • Guides
    • What is my Jira server URL?
    • Jira Test Case Management (TCM) solution
    • How to define the local feature-set to be synchronized
    • Filters and scopes
    • How to use SpecSync from build or release pipeline
    • How to upgrade to a newer version of SpecSync
    • How to attach files to test results
    • Using SpecSync with Cucumber
    • Using SpecSync with Cypress
    • Using SpecSync with Postman
    • Using SpecSync with TestNG
    • Using SpecSync on macOS or Linux
    • Using SpecSync inside a Docker container
    • Migrating from SpecSync v1 to v5
  • Changelog
  • Release Model and Roadmap
  • Downloads
  • Reference
    • Command line reference
      • init
      • upgrade
      • push
      • pull
      • publish-test-results
      • version
    • Configuration reference
      • toolSettings
      • local
      • remote
      • jira
      • knownRemotes
      • synchronization
        • push
        • pull
        • links
        • attachments
        • format
        • fieldUpdates
      • hierarchies
      • publishTestResults
      • specFlow
      • customizations
    • Compatibility
    • Older versions
  • Contact
    • SpecSync Support
    • Troubleshooting
    • FAQ
  • Project Website
Powered by GitBook
On this page
  • Settings
  • Example: Typical configuration for Jira TCM Customization
  • Example: Typical configuration for Zephyr Scale

Was this helpful?

  1. Reference
  2. Configuration reference

jira

This configuration section contains settings to configure the Jira Test Case Management (TCM) solution.

The following example shows the most common options within this section.

{
  ...
  "jira": {
    "tcmSolution": "JiraTcmCustomization",
    "customStepsField": {
      "field": {
        "name": "Steps To Complete"
      }
    },
    "testCaseIssueType": {
      "name": "Test Case"
    },
    "testsLinkName": "tests"
  },
  ...
}

Settings

Setting
Description
Default

jiraProduct

Jira Software product you connect to. Available values: Cloud, DataCenter

automatically detected from the server URL

tcmSolution

The Test Case Management (TCM) customization solution of the Jira project. Available values: JiraTcmCustomization, ZephyrScale

mandatory

testCaseIssueType

The Jira Issue Type used for storing Test Cases.

mandatory for JiraTcmCustomization TCM

customStepsField

Specifies details about how Test Case steps are synchronized to a custom multi-line text field.

  • customStepsField/field/name — The name of the field

  • customStepsField/field/id — The ID of the field

mandatory for JiraTcmCustomization TCM

testsLinkName

The name of the link type used for describing that a Test Case tests a particular requirement. Usual values are tests or tested with

tests

Example: Typical configuration for Jira TCM Customization

{
  "remote": {
    "serverUrl": "https://specsyncdemo.atlassian.net/",
    "project": "MyCalculator",
  },
  "jira": {
    "tcmSolution": "JiraTcmCustomization",
    "customStepsField": {
      "field": {
        "name": "Steps To Complete"
      }
    },
    "testCaseIssueType": {
      "name": "Test Case"
    }
  },
  ...
}

Example: Typical configuration for Zephyr Scale

{
  "remote": {
    "serverUrl": "https://specsyncdemo.atlassian.net/",
    "project": "MyCalculator",
  },
  "jira": {
    "tcmSolution": "ZephyrScale"
  },
  ...
}
PreviousremoteNextknownRemotes

Last updated 2 years ago

Was this helpful?

Configuration reference