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

Was this helpful?

  1. Reference
  2. Configuration reference

synchronization

This configuration section contains synchronization settings.

The following example shows the available options within this section.

{
  ...
  "synchronization": {
    "disableLocalChanges": false,
    "testCaseTagPrefix": "tc",
    "tagPrefixSeparators": [":"],
    "pull": {
      "enabled": true,
      "enableCreatingScenariosForNewTestCases": false
    },
    "links": [
      {
        "targetWorkItemType": "ProductBacklogItem",
        "tagPrefix": "pbi",
        "relationship": "Child"
      },
      {
        "tagPrefix": "bug"
      }
    ],
    "attachments": {
      "enabled": true,
      "tagPrefixes": [
        "wireframe",
        "specification"
      ],
      "baseFolder": "resources/files"
    },
    "format": {
      "prefixBackgroundSteps": true,
      "prefixTitle": true,
      "showParameterListStep": "whenUnusedParameters"
    }
  },
  ...
}

Settings

For sub-section settings, click on the name of the setting for details.

Setting
Description
Default

disableLocalChanges

false

testCaseTagPrefix

The tag prefix for specifying the test cases. E.g. specify testcase for referring to test cases using a tag, like @testcase:P01-T1234.

tc

tagPrefixSeparators

Specifies one or more tag prefix separators to recognize in order to be able to support links like @story=42. For creating tags, the first separator is used.

[":"] (only : can be used as separator)

linkLabelSeparator

Specifies the link label separator in order to be able to support links like @story:42,this_is_the_title.

;

PreviousknownRemotesNextpush

Last updated 1 year ago

Was this helpful?

Disables changing feature files in the local repository. If set to true (called build server mode), only those changes will be performed that do not need any change in the local feature files. Linking new scenarios or pulling changes from test cases will be skipped. Can be overridden by the --disableLocalChanges . See for details.

Settings to configure the push behavior. See

Settings to configure the pull behavior. See for details

Settings to configure how test case links should be updated based on the tags of the scenario. See for details.

Settings to allow attaching files to Test Cases during synchronization using tags. See for details.

Settings to configure the format of the synchronized test case. See for details.

Specifies how the fields of the Test Case that are not managed by SpecSync should be updated. It can contain update rules in "key": <VALUE> format, where key is a field name or identifier and <VALUE> is the value to update to or an update specifier. See for details.

Configuration reference
command line option
Synchronizing test cases from build
push
Pushing scenario changes to Test Cases
pull
Two-way synchronization
links
Linking work items using tags
attachments
Attach files to Test Cases using tags
format
Configuring the format of the synchronized test cases
fieldUpdates
Update Test Case fields