Upgrade OpenRose to Version 0.2.0-120 (Standalone Installation)

 



Ability to locate and go to a specific requirement is extremely important. It allows users and integrated applications to locate requirements related data easily in an effective requirements management tool - OpenRose.

OpenRose is a free and open-source requirements management tool designed to help teams structure and manage complex specifications. In this guide, we’ll walk through upgrading a standalone installation of OpenRose to the latest release, v0.2.0-120, highlighting key steps, compatibility, and new features.

Compatibility: Upgrade from Any Older Version

You can upgrade to OpenRose v0.2.0-120 from any previous version, as long as it’s lower than 0.2.0-120. Whether you're on v0.2.0-69, v0.1.2-243, or an earlier release, the upgrade process remains consistent:

  • Back up your database and configuration files
  • Replace the old API and Web UI folders with the new ones
  • Restart the application using the provided batch file

This makes it easy for users to stay current without needing incremental upgrades.

What’s New in v0.2.0-120?

The headline feature in this release is the introduction of GoTo navigation links, which allow users to jump directly to related records across the system. This dramatically improves traceability and navigation, especially in large-scale requirement sets.

Supported Record Types for GoTo Navigation

GoTo links are now available for seven different data types:

  1. Projects
  2. Requirement Item Types
  3. Requirement Items
  4. Baselines
  5. Baseline Requirement Item Types
  6. Baseline Requirement Items
  7. Orphaned Items

These links streamline workflows by allowing instant access to interconnected records, making it easier to manage dependencies and maintain context.

Step-by-Step Upgrade Instructions

1. Verify Your Current Setup

  • Confirm you're running a standalone installation of OpenRose.
  • Navigate to Settings in your local instance to check your current version (e.g., 0.2.0-69).

2. Backup Your Data

Before upgrading, it’s essential to back up your SQL Server database:

  • Open SQL Server Management Studio.
  • Locate your OpenRose database.
  • Right-click → Tasks → Backup.
  • Choose a disk location (e.g., C:\ or D:) and save a full backup.

Also, back up your appsettings.json files if you’ve customized them:

  • API folder:(e.g. C:\OpenRose\API\appsettings.json)
  • Web UI folder: (e.g. C:\OpenRose\WebUI\appsettings.json)

If you're using environment variables for configuration (instead of JSON files), you can skip this step.

3. Stop the Running Services

  • Stop both the Web UI and API services before proceeding.

4. Download the Latest Release

  • Visit the OpenRose GitHub Releases.
  • Download the latest API and Web UI zip files for your system architecture (e.g., x64).

5. Replace Old Installation Files

  • Delete the existing API and Web UI folders from your installation directory (e.g., C:\OpenRose).
  • Move the downloaded zip files into the same directory.
  • Extract both zip files in place.
  • Delete the zip files after extraction.

6. Start the Application

  • Navigate to the Web UI folder.
  • Run StartOpenRose.bat to launch both the API and Web UI.
  • Allow network access if prompted (optional for local setups).

Post-Upgrade Verification

Once the application is running:

  • Visit your local instance (e.g., http://localhost:7673)
  • Go to Settings to confirm the version is now 0.2.0-120
  • Explore the new GoTo navigation links in your projects, baselines, and orphaned items

Final Thoughts

Upgrading to OpenRose v0.2.0-120 brings smoother navigation and better traceability to your requirements management workflow. With just a few careful steps, your standalone installation will be up-to-date and ready to leverage the latest features.


Thank you for supporting OpenRose. We’re excited to see how you’ll use the GoTo feature to streamline your workflows and enhance your project management experience.

OpenRose, a free and open-source requirements management application / tool. For more information, visit 

https://github.com/openrose




Comments

Post a Comment

Popular posts from this blog

Introduction to OpenRose - Requirements Management

Image
Watch it on YouTube at : https://www.youtube.com/watch?v=P0x3ZaHg8sA OpenRose - Requirements Management Application VIDEO TRANSCRIPT Hello, and thanks for joining in for the launch of OpenRose, an open-source requirements management application. The main purpose is to help users and teams "do it right" and ultimately reduce waste. OpenRose is released on GitHub at [github.com/OpenRose](https://github.com/OpenRose). Users can look at the source code and documentation at the same location. Let me do a quick demo of the application. In this environment, I'm using Windows 11 on a desktop computer, not a server. I have installed IIS and deployed a web deployment package over IIS. When you connect to OpenRose, on the homepage, you will see a welcome message like this: "Welcome to OpenRose." One would start by creating a new project. For this demo, I've created two separate projects. The first project is a small example of how I converted a document published b...
Read more

What is Requirement?

Image
What is Requirement? OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=3qQzKbfvRPA Video Transcript :   Hi, welcome to OpenRose, an open-source and free requirements management application. Please visit https://github.com/openrose for more information. Let's go to the project dashboard, and this time, let's open a deep hierarchical level project. This is just a demo project, so when I open that project in the TreeView and start expanding the project, I can see some sample item types along with a Parking Lot, which is the system item type. Inside item type one, I have a top-level item, then item one and item two, which are broken down into further items. You can see I've given the names which indicate a kind of logical hierarchical structure in the name. Here, you can see L1, L2, L3, L4—that's the level. The project is considered as level one, and item ...
Read more

Details View - OpenRose - Requirements Management

Image
    Details View OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=FC67o7lUy3I Video Transcript : Hello. OpenRose is a requirements management application, which is freely available and published on GitHub. Simply go to github.com/openrose to find more. Today, we will discuss the Details View. When you go into the Projects section where you can see your list of projects, there are two main views: the Tree View and the Details View. When I click on Details View, I enter the project one level at a time, or I exit the project one level at a time. Inside the project, we know that there are item types. In this particular view, we can see that I have a parking lot, which is a system item type, and four other item types that I have created. This is a public document published by Barkley's Bank, which I have tried converting into some sort of specification or requirem...
Read more