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
  • Limitations of the Free Edition
  • Limitations of the Standard Edition
  • Enterprise features
  • Enterprise support
  • EULA

Was this helpful?

Licensing

PreviousPlugin listNextGuides

Last updated 2 years ago

Was this helpful?

SpecSync provides different licensing options including a free usage for smaller projects. For details and pricing, please check the .

Please send your questions or license inquiries to .

The licenses are provided as a license file. SpecSync tries to find the license file in the project folder (where the specsync.json configuration file is located). Since the license files are project or enterprise specific, these can be safely checked in to the source control.

The location of the license file (absolute or relative to the project folder) can also be specified with the --license option of the or in the toolSettings/licensePath setting of the if necessary. You can also consider to configure the license path in the .

The SpecSync license files are digitally signed text files. You can open them with a text editor (e.g. Notepad) to check the expiry date, the edition and other details.

Limitations of the Free Edition

  • Maximum 30 scenarios can be synchronized

  • Enterprise features cannot be used

Scenario Outlines count as one scenario.

Limitations of the Standard Edition

  • Maximum 300 scenarios can be synchronized

  • Enterprise features cannot be used

Scenario Outlines count as one scenario.

Enterprise features

Enterprise support

EULA

Two-way synchronization (using the pull command). See for details.

All

The Service Level Agreement (SLA) for the support services for SpecSync for Jira Enterprise license holders can be downloaded from .

The End User License Agreement (EULA) can be downloaded .

SpecSync for Jira uses 3rd party software libraries, please find their licenses at .

Two-way synchronization
customization features
here
here
http://speclink.me/specsync3rdpartylic
available plans
specsync@specsolutions.eu
synchronization tool
configuration file
user-specific configuration file