🌷OpenRose

  Server‑Side Offline Data File Views introduce a simple but transformative capability to OpenRose: the ability to host exported project data directly on the server and make it instantly accessible to any authorized user. This dramatically improves how teams share information, collaborate, and maintain visibility across projects. Here are the key reasons this feature stands out: Zero‑Complexity Hosting You export a JSON file and place it in a server folder. That’s it. Accessible to All Team Members Anyone with access to the OpenRose instance can open the hosted file—no emailing, no file transfers, no setup. Perfect for Non‑Technical Contributors If someone can write Markdown, they can create content that can be exported and hosted. Centralized and Always Available Hosted files remain accessible even if the SQL Server or API layer is offline. Ideal for Documentation and Reference Material Requirements, onboarding guides, snapshots, and structured notes can all be hosted a...

  A Smarter Way to Organise Requirements: Introducing Flexible Tagging in OpenRose Why This Feature Matters Managing large sets of requirements often becomes messy — especially when teams need to group items by release cycle, business area, priority, location, or any other meaningful category. Traditional tools force rigid naming rules or limited classification options, making it harder to keep projects organised. The new Tagging capability in OpenRose solves this problem by giving you a simple, expressive way to label and retrieve requirements using terminology that matches how your team actually works. Teams benefit immediately because: Tags reflect real project language — not system‑imposed formats Search and filtering become faster and more meaningful Non‑technical contributors can add and update tags easily Tags remain consistent across baselines, exports, imports, and offline views Complex projects become easier to navigate and maintain As the produ...

  In modern requirements management, teams need flexibility. Not everyone has access to the full OpenRose installation, and not every scenario allows a live connection to the repository. That’s exactly why OpenRose introduces Client‑Side JSON Offline Data File Views — a feature designed to make sharing, reviewing, and exploring requirements easier than ever. This capability lets you export your project (or any part of it) into a compact JSON file and share it with anyone who has access to the OpenRose Web UI. The recipient can then open the file locally and browse the data exactly as if they were connected to the live repository — but in a safe, read‑only mode. Let’s break down what makes this feature so powerful. 1. A True Read‑Only Experience — With Full Visibility Recipients of a JSON offline file: Cannot edit, modify, delete, or move anything Cannot perform exports, imports, or data operations Cannot modify traceability data Cannot create new Baselines or perform Inc...