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?

Introduction to SpecSync for Jira

NextGetting started

Last updated 3 months ago

Was this helpful?

Many teams being currently in a transformation process towards using agile and BDD have to face the problem that the new specification artifacts and reports have to be integrated into the existing tool chain. Many of such teams use Jira-full where the concept of Test Cases and Test Runs can be used to represent and trace the testing activities.

SpecSync for Jira integrates the BDD process with Jira by connecting and synchronizing the BDD scenarios with Test Cases and by publishing test execution results to Jira in a way that the test result remains connected to the related Test Case. With this the development and testing activities remain transparent and traceable for all stakeholders in Jira.

SpecSync supports any tool that uses the Gherkin language for describing the BDD scenarios, for example SpecFlow, Reqnroll or Cucumber (see more details in the page).

SpecSync helps people to stay in sync with Azure DevOps and Jira since 2016 and by now it is used by many organizations around the globe.

Your Data in Your Hands

SpecSync makes direct connection between the machine that runs SpecSync and the remote Azure DevOps or Jira server. The scenario or Test Case data is not transferred to or processed by premises of Spec Solutions.

Project site: .

This documentation contains the necessary information to configure and use SpecSync. If you are new to SpecSync, we recommend starting with the .

Compatibility
https://www.specsolutions.eu/specsync/
Getting Started Guide