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. Guides

How to upgrade to a newer version of SpecSync

PreviousHow to use SpecSync from build or release pipelineNextHow to attach files to test results

Last updated 2 years ago

Was this helpful?

If you are using an older version of SpecSync it is recommended to upgrade it to a more recent version. If your version is older than 365 days, SpecSync will even remind you for upgrading.

Before upgrade we recommend checking the page and choose the version you would like to upgrade to. Upgrading to a newer update version (only the third number is different, e.g. 3.2.9 to 3.2.12) can be done without planning and consideration, but for upgrading to a newer main version you should check the for compatibility notes. You can find more details about the release types in the page.

The upgrade procedure depends on how you have . In this list we provide the upgrade procedure for the most common installation options. In the examples we assume you want to upgrade to v3.2.12, but you need to replace this with the version you have chosen.

  • If you have installed SpecSync as a (you use it with the dotnet specsync command), you need to invoke dotnet tool update SpecSync.Jira --version 3.2.12 from your local repository. Make sure you commit the changes to the dotnet-tools.json file and ask your team mates to perform a dotnet tool restore command after they pulled your change.

  • If you have installed as a (you invoke SpecSync4Jira.cmd or you invoke SpecSync4Jira.exe from the tools folder of the NuGet package), you need to update the NuGet package with dotnet add package SpecSync.Jira --version 3.2.12 or from the Package Manager in Visual Studio.

  • If you use the downloaded (you invoke SpecSync4Jira or SpecSync4Jira.exe from an arbitrary folder), you need to download a newer version from the page.

  • If you use the SpecSync official (you invoke a docker run command for the specsolutions/specsync4jira, specsolutions/specsync4jira:3.2 or specsolutions/specsync4jira:3.2.9 image), you need to either use a specific tag (e.g. specsolutions/specsync4jira:3.2.12) or make sure you have the latest version of the image using the docker pull specsolutions/specsync4jira:3.2 command.

If you have problems or questions related to upgrading SpecSync, please contact .

Changelog
Changelog
Release Model and Roadmap
installed SpecSync
.NET Tool
.NET Console App
SpecSync.Jira.Console
binaries
Downloads
Docker image
support