<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by OpenRose on Medium]]></title>
        <description><![CDATA[Stories by OpenRose on Medium]]></description>
        <link>https://medium.com/@openrose?source=rss-a745b037e96b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lEmqfZs-8faNImwbT-PbtA.png</url>
            <title>Stories by OpenRose on Medium</title>
            <link>https://medium.com/@openrose?source=rss-a745b037e96b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:35:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@openrose/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Data Tagging in Mermaid Diagrams]]></title>
            <link>https://medium.com/@openrose/data-tagging-in-mermaid-diagrams-c015049e4fc2?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c015049e4fc2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[mermaid-diagram]]></category>
            <category><![CDATA[tagging]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[business-analyst]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 10:33:52 GMT</pubDate>
            <atom:updated>2026-11-19T10:33:52.596Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5hGKSr1mwRI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5hGKSr1mwRI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5hGKSr1mwRI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/136e3a7248c0e95cbeaa37f0d6715797/href">https://medium.com/media/136e3a7248c0e95cbeaa37f0d6715797/href</a></iframe><p>Presenting requirements to management teams and stakeholders is an important part of successful requirements management. While detailed requirements are essential for implementation teams, management often needs a much simpler, high-level view of the project to understand its scope, structure, priorities, and estimated costs.</p><p>This is where visual representations such as flowcharts and mind maps become particularly useful.</p><p>At <strong>OpenRose</strong>, we understand that many users rely on Mermaid flowcharts to transform their requirements breakdown structures into visual diagrams that can be used during management presentations, stakeholder discussions, and project workshops.</p><p>We also know that tags play an important role in classifying and organising requirements. Tags allow teams to categorise information based on different purposes, business areas, priorities, or other classification criteria.</p><p>To make these visual representations even more useful, we have introduced a new capability in OpenRose: <strong>the ability to include requirement tags and estimation information directly in exported Mermaid flowcharts.</strong></p><p>Let’s explore how this works and how it can improve the way you communicate project information.</p><h3>Why Use Mermaid Flowcharts for Requirements Management?</h3><p>A requirements breakdown structure can contain a significant amount of information. Although this structure is useful for managing detailed requirements, presenting the entire hierarchy in a traditional tabular or tree format may not always be the best approach when communicating with management teams.</p><p>Management teams often need to understand:</p><ul><li>What are the major areas of the project?</li><li>How are requirements organised?</li><li>Which categories or classifications apply to different requirements?</li><li>What are the estimated costs or effort associated with different areas?</li><li>How does a particular requirement fit into the overall project structure?</li></ul><p>Mermaid flowcharts provide an effective way to communicate this information visually.</p><p>OpenRose already supports exporting project information as Mermaid flowcharts. Users can select a parent record, such as an entire project, an item type, or a requirement containing sub-requirements, and generate a visual representation of the underlying requirements structure.</p><p>You can even export an individual requirement if you only want to visualise a specific part of your project.</p><p>The exported Mermaid content can then be copied into tools that support Mermaid diagrams, including the free online Mermaid Live Editor.</p><p>This makes it easy to transform your requirements data into presentation-ready visual diagrams without manually recreating the structure.</p><h3>The New Capability: Include Tags in Mermaid Flowcharts</h3><p>One of the useful capabilities in OpenRose is the ability to apply tags to requirements.</p><p>Tags allow users to classify requirements using different naming conventions, languages, symbols, and other classification techniques.</p><p>For example, a requirement might contain multiple tags representing different aspects of the information.</p><p>These tags are already visible within the requirement details in OpenRose. They are also included when the requirement data is exported in JSON format or viewed in read-only mode.</p><p>However, until now, this tagging information was not included in the exported Mermaid flowcharts.</p><p>This meant that when users generated a Mermaid diagram, they could see the requirement names and their hierarchical relationships, but the associated tags were missing.</p><p>We have now addressed this limitation.</p><p><strong>OpenRose now allows users to include tag information when generating Mermaid flowcharts.</strong></p><h3>How to Include Tags in an Exported Mermaid Flowchart</h3><p>Let’s use our Charity Fundraising demonstration project to understand how this works.</p><p>First, we navigate to the project and open the requirements breakdown structure in Tree View.</p><p>Here, we can see the project data organised into a structured hierarchy.</p><p>Let’s select the first requirement, which defines the fundraising goals.</p><p>When we open the requirement details, we can see the different tags that have been applied.</p><p>These tags are useful for classifying the requirement and providing additional context beyond its actual name.</p><p>To generate a Mermaid flowchart, we navigate to the project’s Action menu and select the option to export the project as a Mermaid flowchart.</p><p>OpenRose generates the Mermaid text representing the project’s requirements structure.</p><p>We can copy this text and paste it into the <a href="https://www.blogger.com/blog/post/edit/7340859463154657980/1655117732167988161#">Mermaid Live Editor</a>.</p><p>The editor immediately generates a visual flowchart based on the exported requirements data.</p><p>We can see the complete requirements hierarchy, including the relationships between parent and child requirements.</p><p>Mermaid diagrams also support clickable links. This means users can click on a particular requirement in the diagram and navigate directly to the corresponding requirement in OpenRose.</p><p>However, in the original export, the tags are not displayed.</p><p>To include them, we simply return to the Mermaid export screen.</p><p>You will now find a new checkbox labelled <strong>Include Tags</strong>.</p><p>Enable this option and regenerate the Mermaid flowchart.</p><p>Copy the newly generated Mermaid content and paste it into the Mermaid Live Editor.</p><p>This time, the result is different.</p><p>All the tags associated with the requirements are now displayed directly within the flowchart, following the same order in which they were applied to the requirements.</p><h3>Visually Distinguishing Tags from Requirement Names</h3><p>We have also paid attention to how the tags are presented in the generated diagrams.</p><p>Rather than simply appending tags to requirement names, OpenRose uses background colours and formatting to make them visually distinct.</p><p>This is important because users should be able to immediately recognise which information represents the actual requirement name and which information represents its associated tags.</p><p>The result is a much more informative and visually appealing Mermaid diagram.</p><p>This is particularly useful when presenting high-level project information to management teams.</p><p>Instead of showing only requirement names, you can now communicate the additional classifications and context that your team has applied to the underlying requirements.</p><h3>Include Estimations Along with Tags</h3><p>Tags are not the only information that can be included in Mermaid flowcharts.</p><p>OpenRose also supports including estimation information in the exported diagrams.</p><p>This is particularly useful when presenting project scope and estimated costs to management teams.</p><p>For example, in our Charity Fundraising project, we have captured some sample estimation values using dollars as the estimation unit.</p><p>A few examples include:</p><ul><li>Defining fundraising goals: $100</li><li>Identifying target audience: $50</li><li>Other related requirements with their respective estimation values.</li></ul><p>These individual estimations contribute to the overall estimation of their parent requirements.</p><p>For example, the Pre-Fundraising Preparation section has a roll-up estimation of $530.</p><p>Similarly, the overall Charity Fundraising project also has a roll-up estimation of $530.</p><p>OpenRose allows users to recalculate roll-up estimations to ensure that the estimation values are correctly consolidated throughout the requirements breakdown structure.</p><p>For our demonstration, we recalculate the roll-up estimations to ensure that the entire requirements hierarchy reflects the expected values.</p><p>Once this is complete, we can return to the Mermaid export screen.</p><p>This time, we enable the options to include both <strong>Tags</strong> and <strong>Estimations</strong>.</p><p>When we generate the Mermaid flowchart and paste the exported content into the Mermaid Live Editor, we can now see both types of information displayed alongside the requirements.</p><p>The resulting diagram provides a much richer representation of the project.</p><p>Users can see:</p><ul><li>The hierarchical structure of the requirements.</li><li>The actual requirement names.</li><li>The associated tags and classifications.</li><li>The estimation values associated with the requirements.</li></ul><p>This provides management teams with a much better understanding of the project without requiring them to navigate through the detailed requirements breakdown structure.</p><h3>Better Management Presentations and Stakeholder Communication</h3><p>The ability to include tags and estimations in Mermaid flowcharts brings several practical benefits.</p><h3>1. Communicate More Than Just Requirement Names</h3><p>A traditional requirements flowchart may show only the names of requirements and their relationships.</p><p>However, requirement names alone may not provide enough information for management teams to understand the context.</p><p>By including tags, you can communicate how requirements have been classified and grouped.</p><p>This could be based on business areas, functional categories, departments, priorities, or other classification approaches used by your organisation.</p><h3>2. Present Estimation Information Visually</h3><p>Including estimation values makes Mermaid flowcharts more useful during project planning and management discussions.</p><p>Instead of manually calculating and adding estimation information to presentation diagrams, users can generate the diagrams directly from OpenRose.</p><p>This helps ensure that the information presented is consistent with the estimation data maintained in the requirements management system.</p><h3>3. Reduce Manual Diagram Maintenance</h3><p>One common challenge with manually maintained diagrams is keeping them synchronised with the actual project data.</p><p>Whenever requirements change, someone has to remember to update the corresponding diagram.</p><p>This can become difficult, particularly when working with large projects or multiple stakeholders.</p><p>With OpenRose, the requirements remain the primary source of information.</p><p>Users can simply regenerate the Mermaid flowchart whenever they need an updated visual representation.</p><p>There is no need to manually recreate the requirements hierarchy, add tags, or update estimation information in a separate diagram.</p><h3>4. Improve Management and Stakeholder Discussions</h3><p>A well-structured visual representation makes it easier for management teams and stakeholders to understand project information.</p><p>Whether you are presenting to management, marketing teams, sales teams, customers, or implementation stakeholders, having additional context directly within the diagram can help reduce confusion.</p><p>Instead of asking stakeholders to interpret requirement names and guess their meaning, you can provide a much clearer representation of the underlying information.</p><p>This supports more informed discussions, better feedback, and more effective decision-making.</p><h3>5. Keep Requirements Data and Visualisations Connected</h3><p>Perhaps the most important benefit is that you can maintain all your important information in one place.</p><p>OpenRose remains the central source for your requirements, tags, estimations, and hierarchical structure.</p><p>Mermaid flowcharts become a convenient way to visualise and communicate that information rather than another manually maintained source of project data.</p><p>This approach helps teams avoid unnecessary duplication and reduces the effort involved in keeping multiple representations of the same project up to date.</p><h3>A More Effective Way to Present Requirements with OpenRose</h3><p>We believe that requirements management should not stop at capturing and organising requirements.</p><p>It should also make it easier for teams to communicate, collaborate, and make informed decisions using the information they have captured.</p><p>The ability to export tags and estimation information directly into Mermaid flowcharts is another step towards making OpenRose a more powerful and flexible Requirements Management Tool.</p><p>Whether you are preparing a management presentation, conducting a project workshop, discussing requirements with customers, or reviewing project estimations with stakeholders, you can now generate richer visual diagrams directly from your requirements data.</p><p>Most importantly, you do not need to maintain separate diagrams manually. Simply maintain your information in OpenRose and use its Mermaid export capability whenever you need a visual representation.</p><h3>Try OpenRose — A Free and Open-Source Requirements Management Tool</h3><p>OpenRose is a <strong>free and open-source Requirements Management Tool</strong> designed to help individuals and organisations manage their requirements and related project information.</p><p>We believe that professional requirements management capabilities should be accessible to everyone, without the financial barriers often associated with commercial requirements management platforms.</p><p>With OpenRose, you can explore a flexible approach to requirements management while benefiting from features that support requirements organisation, classification, estimation, project management, baselines, and visualisation.</p><p>We are continuously enhancing the platform based on practical requirements management needs and feedback from our users.</p><p>The addition of tags and estimations to Mermaid flowcharts is just one example of how we are making requirements information easier to understand, communicate, and use.</p><h3>Give OpenRose a Try!</h3><p>If you are looking for a free and open-source Requirements Management Tool, explore what OpenRose has to offer.</p><p>Discover its capabilities, try its features, and see how it can support your requirements management activities.</p><p><strong>Manage your requirements in one place. Visualise your project structure. Communicate with confidence.</strong></p><p>Visit the OpenRose website to learn more and get started.</p><blockquote><strong><em>OpenRose</em></strong><em>, a free and open-source requirements management application / tool. For more information, visit</em></blockquote><blockquote><a href="https://github.com/openrose"><em>https://github.com/openrose</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-cMUc75ygzXJUx7JPjS-uA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c015049e4fc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preserving the Position of Parking Lot Item Types while Exporting and Importing Data]]></title>
            <link>https://medium.com/@openrose/preserving-the-position-of-parking-lot-item-types-while-exporting-and-importing-data-28d6a9d99a46?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/28d6a9d99a46</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[traceability]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 13:01:24 GMT</pubDate>
            <atom:updated>2026-11-17T13:01:24.330Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNGWMNfDLzbA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNGWMNfDLzbA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNGWMNfDLzbA%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/50bbc74b0b6ddbbe07b419937de32c1f/href">https://medium.com/media/50bbc74b0b6ddbbe07b419937de32c1f/href</a></iframe><p>Managing requirements and project information effectively is about more than simply storing data. It is equally important to maintain the structure, organisation, and relationships that make that data meaningful.</p><p>In requirements management, even seemingly small changes to how information is organised can affect the way teams understand and manage their projects.</p><p>At <strong>OpenRose</strong>, we continuously improve the platform to make requirements management easier, more reliable, and more flexible. One such improvement addresses an important aspect of project data management: <strong>preserving the position of system item types when exporting and importing projects and baselines.</strong></p><p>Let’s explore what this means, why it matters, and how the latest enhancement works.</p><h3>Understanding System Item Types in OpenRose</h3><p>OpenRose uses item types to organise and categorise information within a project.</p><p>When creating a new project, OpenRose automatically provides a predefined system item type called <strong>Parking Lot</strong>.</p><p>Unlike custom or user-defined item types, Parking Lot is a system item type. This means certain properties, such as its name, status, and description, cannot be modified in the same way as those of user-defined item types.</p><p>You can easily distinguish between the two types:</p><ul><li><strong>User-defined item types:</strong> These are created by users and can be customised to suit individual project requirements.</li><li><strong>System item types:</strong> These are predefined by OpenRose and provide specific functionality within the application.</li></ul><p>The Parking Lot item type is an example of a system item type. It is automatically included whenever a new project is created.</p><h3>Why Is the Position of an Item Type Important?</h3><p>OpenRose provides flexibility in organising item types within a project.</p><p>When you create a new custom item type, it is automatically added to the bottom of the existing list. However, users are not restricted to this default arrangement.</p><p>Using the Details view or the <strong>Move Item Type</strong> option, users can easily reposition item types to suit their preferred project structure.</p><p>For example, a “Charity Fundraising Project” might have the following arrangement:</p><ol><li>Pre-Fundraising</li><li>Parking Lot</li><li>Fundraising Event Execution</li><li>Post-Fundraising Activities</li></ol><p>This flexibility allows teams to organise their projects in a way that makes sense for their workflows.</p><p>However, there was previously an issue when exporting and importing projects.</p><h3>The Challenge: Maintaining Item Type Positions During Import and Export</h3><p>Previously, when a project was exported and subsequently imported into OpenRose, the position of the Parking Lot system item type was not necessarily preserved.</p><p>The import process recreated the project and its associated item types. However, user-defined item types were added to the bottom of the list, which could result in the Parking Lot item type appearing in a different position from its original arrangement.</p><p>For example, even if Parking Lot was originally positioned at the bottom of the list, importing the project could cause it to appear at the top.</p><p>Although the underlying item types were retained, the original organisation of the project was not always maintained.</p><p>This could be inconvenient for users who rely on a specific ordering of item types to organise their project information.</p><h3>The Enhancement: Preserve the Original Position of Parking Lot</h3><p>We have now enhanced OpenRose to address this behaviour.</p><p><strong>OpenRose now preserves the position of the Parking Lot system item type when exporting and importing project data.</strong></p><p>The application remembers where the Parking Lot item type was positioned at the time of export and restores it to the same position when the data is imported.</p><p>This means users can maintain their preferred project structure without having to manually reposition the system item type after every import.</p><h3>Testing the Improvement with Project Export and Import</h3><p>Let’s consider a practical example using a Charity Fundraising project.</p><p>First, we have a project containing several custom item types along with the Parking Lot system item type.</p><p>For our initial test, we position Parking Lot at the bottom of the list.</p><p>We then export the entire project using the project’s Action menu.</p><p>Once the export is complete, we navigate to the Import screen, select the exported data, and import it.</p><p>OpenRose creates a new project from the imported data.</p><p>When we open the newly imported project and inspect its item types, we can see that Parking Lot remains in its original position at the bottom of the list.</p><p>To test the enhancement further, we change the position of Parking Lot in the original Charity Fundraising project.</p><p>This time, we move it somewhere in the middle of the list, between two user-defined item types.</p><p>We export the project again and import the newly generated export file.</p><p>Once the import is complete, we inspect the newly created project.</p><p>The result is exactly what we expect: <strong>Parking Lot appears in the same middle position that it occupied in the original project when the data was exported.</strong></p><p>This confirms that OpenRose now preserves the position of the system item type, regardless of where it is located within the project.</p><h3>Does This Also Work with Baselines?</h3><p>Yes!</p><p>Preserving item type positions is not limited to standard project exports. The same enhancement also applies when working with baselines.</p><p>In OpenRose, a baseline represents a snapshot of project data at a particular point in time.</p><p>This allows users to capture and preserve a particular state of their project for future reference.</p><p>For our demonstration, we create a baseline of the Charity Fundraising project while Parking Lot is positioned in the middle of the item type list.</p><p>We give the baseline the name:</p><p><strong>Baseline with Parking Lot in the Middle Position</strong></p><p>After creating the baseline, we can view its contents and verify the arrangement of the item types.</p><p>We then export the entire baseline data.</p><p>It is important to understand that importing an exported baseline does not recreate it as a baseline within the existing repository.</p><p>A baseline is a snapshot of data. When its exported JSON data is imported, OpenRose creates a new project instead. This allows users to work with and modify the imported data as a separate project.</p><p>Once the baseline export has been imported, we navigate to the project list and open the newly created project.</p><p>We can now see that the Parking Lot system item type is still positioned between the two user-defined item types, exactly as it was when the baseline was created and exported.</p><p>This demonstrates that the position of the system item type is preserved not only during standard project export and import operations but also when working with baseline data.</p><h3>Why This Improvement Matters</h3><p>Maintaining the structure of project data is an important part of effective requirements management.</p><p>This enhancement provides several practical benefits:</p><ul><li><strong>Consistent project organisation:</strong> Item types retain their original positions when project data is transferred.</li><li><strong>Reliable data migration:</strong> Users can export and import projects without worrying about the Parking Lot item type unexpectedly changing position.</li><li><strong>Better baseline management:</strong> The same behaviour is supported when exporting and importing baseline data.</li><li><strong>Less manual intervention:</strong> Users do not need to spend additional time rearranging item types after importing projects.</li><li><strong>Preserved system functionality:</strong> Parking Lot continues to be recognised as a system item type rather than being treated as a regular user-defined item type.</li></ul><p>These improvements contribute to a more predictable and consistent experience when managing project information in OpenRose.</p><h3>Experience Better Requirements Management with OpenRose</h3><p>OpenRose is a <strong>free and open-source Requirements Management Tool</strong> designed to help individuals and organisations manage requirements and related project information.</p><p>We believe that effective requirements management should be accessible to everyone, without the financial barriers often associated with commercial requirements management platforms.</p><p>By making OpenRose free and open source, we aim to give users the flexibility to explore, adopt, and adapt a requirements management solution that supports their needs.</p><p>We are continuously working to improve the platform, introducing enhancements that make managing project information more intuitive, reliable, and efficient.</p><p>This improvement to system item type positioning is another step towards that goal.</p><h3>Give OpenRose a Try!</h3><p>If you are looking for a free and open-source Requirements Management Tool, why not explore OpenRose?</p><p>Discover its capabilities, experiment with its features, and see how it can support your requirements management activities.</p><p><strong>Explore OpenRose, simplify requirements management, and take control of your project information.</strong></p><p>Visit the OpenRose website to learn more and get started.</p><blockquote><strong>OpenRose</strong>, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSRdZPrOIoWLu0N6X6oN6w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28d6a9d99a46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Digital Menu for Every Restaurant & Food Businesses]]></title>
            <link>https://medium.com/@openrose/a-simple-digital-menu-for-every-restaurant-food-businesses-c7d52562ef55?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7d52562ef55</guid>
            <category><![CDATA[restaurant-menu]]></category>
            <category><![CDATA[cafe-menu]]></category>
            <category><![CDATA[digital-menu]]></category>
            <category><![CDATA[foodies]]></category>
            <category><![CDATA[qr-code-menu]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 21:22:17 GMT</pubDate>
            <atom:updated>2026-10-12T23:31:38.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SH_Q7HcYlq70me5LD-A6kw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpTK9qK0F_FE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FpTK9qK0F_FE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpTK9qK0F_FE%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa346987396c2a740a11c0976e383cdd/href">https://medium.com/media/fa346987396c2a740a11c0976e383cdd/href</a></iframe><p><strong>TRY OUT SAMPLE MENU BY SCANNING FOLLOWING QR CODE…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*FweLG95Svm72ptGxgyp9Rg.png" /></figure><p>If QR Code does not work then try this direct web link … <a href="https://restaurantmenu-c7c5hchuakatchgu.uksouth-01.azurewebsites.net/">Sample Menu with OpenRose</a>.</p><p>Whether you run a restaurant, café, food stall, food van or catering business, trying the sample is an easy way to see how <strong>OpenRose</strong> could help you share your menu with customers.</p><p>A great menu helps customers decide what to order — and it shouldn’t take a complicated system or a big budget to share one online. <strong>OpenRose</strong> makes it easy for restaurants, cafés, food stalls, food vans, caterers and other food businesses to create a digital menu customers can browse on their phone or tablet.</p><p>With <strong>OpenRose</strong>, your menu can be organised into sections such as starters, mains, desserts, drinks and set menus, with space for dish photos, descriptions, prices and useful details like allergens, spice levels and dietary choices. Customers can open it in a web browser by scanning a QR code — no app download required.</p><p>Whether you run a busy restaurant or a small food stall, <strong>OpenRose</strong> offers a straightforward way to put your menu online and make it easy to find. It focuses on what many food businesses need most: a clear, attractive digital menu that’s simple to share.</p><p>For stronger search visibility, use <strong>food business</strong> as the broad term, supported by phrases such as <strong>restaurant</strong>, <strong>café</strong>, <strong>food stall</strong>, <strong>food van</strong>, <strong>eatery</strong> and <strong>catering business</strong>. “Food business” is clearer and more widely applicable than “food outlet.”</p><h3>Key Benefits of OpenRose Digital Menu</h3><p><strong>OpenRose</strong> works as <strong>online catalogue software for digital food menus</strong>, giving food businesses a simple way to present dishes and drinks without needing a complex ordering or payment system.</p><ul><li><strong>Create menus for every occasion:</strong> Easily customise your menu for seasonal offers, parties, set menus and other special occasions. You can create menus to suit different events or times of year.</li><li><strong>Designed for touch screens:</strong> Customers can browse the menu on a phone, tablet or other touch-screen device, making it easy to explore while in your restaurant, café or food stall.</li><li><strong>No app download required:</strong> Your customers can view the menu in their web browser without installing an app or creating an account.</li><li><strong>Easy access with a QR code:</strong> Place a QR code on tables, counters, takeaway packaging or promotional materials so customers can open your menu with a quick scan.</li><li><strong>Quick to update:</strong> Change menu details when dishes, prices or availability change, helping you keep the information customers see up to date.</li><li><strong>Show important food information:</strong> Add allergen, spice-level and dietary indicators to help customers quickly spot details that matter to them.</li><li><strong>Share it online:</strong> Link your digital menu from your website and make it accessible through a web browser, giving customers another convenient way to see what you offer.</li><li><strong>Make it your own:</strong> Add a welcome message and your business logo to give customers a branded experience from the moment they open the menu.</li><li><strong>Open-source software:</strong> <strong>OpenRose</strong> is open source, making it an option for businesses and IT teams who value flexibility and control over how software is used and deployed.</li><li><strong>Choose a deployment approach:</strong> <strong>OpenRose</strong> supports online and offline deployment models, so your team can choose an approach that suits your setup.</li><li><strong>Get help with setup:</strong> Your IT team can assist with deployment, or you can contact <strong>OpenRose</strong> for support.</li><li><strong>Bring your dishes to life:</strong> Add real photos of your food and drinks so customers can see what’s on offer. You can also use image-editing or design tools to prepare polished, appealing visuals for your menu.</li><li><strong>Create as many menus as you need:</strong> <strong>OpenRose</strong> has no restriction on the number or size of menus, so you can organise a wide-ranging selection or create separate menus for different occasions.</li><li><strong>Choose the format that fits:</strong> Present your menu as a single page or use individual pages for dishes and drinks, depending on how you want customers to browse.</li><li><strong>Keep things simple:</strong> <strong>OpenRose</strong> focuses on displaying your menu rather than connecting to payment or ordering systems. That keeps the setup and ongoing maintenance straightforward for businesses that need a digital catalogue.</li></ul><h3>OpenRose: Free Software, With Support When You Need It</h3><ul><li><strong>No software fee:</strong> <strong>OpenRose</strong> is free to use as a digital menu application. Food businesses can use it to create and share their menus without paying for the software itself.</li><li><strong>Open source and available on GitHub:</strong> The application is open source and available on GitHub, giving businesses and their IT teams access to the project and the flexibility to work with it.</li><li><strong>Built with modern web technologies:</strong> <strong>OpenRose</strong> uses modern web technologies to deliver a browser-friendly menu that customers can access online, including by scanning a QR code.</li><li><strong>Created to support food communities:</strong> <strong>OpenRose</strong>’s purpose is to help people who serve food with love and care share their menus and food creativity with more customers — without a software cost getting in the way.</li><li><strong>Use your existing IT support:</strong> If your restaurant already has an IT team or a trusted IT provider, they can help deploy <strong>OpenRose</strong> as your digital menu using your existing support arrangements.</li><li><strong>Optional setup and ongoing help:</strong> If you’d like assistance, support is available remotely for initial setup, ongoing needs and hosting your digital menu on the internet. The <strong>OpenRose</strong> application itself is free; hosting and optional support arrangements can be discussed separately.</li></ul><h3>Give OpenRose a Try</h3><ul><li><strong>Test it for a weekend or a week:</strong> Try <strong>OpenRose</strong> in your restaurant, café, food van or stall for a short period. A small trial can help you see how a digital menu fits into your day-to-day service.</li><li><strong>Start with a few menu items:</strong> You don’t need to prepare your entire menu to get started. Add a selection of dishes and drinks, then see how they look and feel in the digital format.</li><li><strong>Share the QR code:</strong> Put the QR code somewhere easy to spot and invite customers to scan it. They can open the menu in their browser and browse without downloading an app.</li><li><strong>Ask staff and customers what they think:</strong> Find out whether the menu is easy to use, whether the information is clear and what could make the experience better. Their feedback can help you decide if <strong>OpenRose</strong> suits your business.</li><li><strong>Explore it without a long-term commitment:</strong> The <strong>OpenRose</strong> application itself is free to use, so you can try it and decide whether it’s useful for your business. If it isn’t the right fit, you can simply stop using it.</li></ul><p><strong>Start small, scan the code and see what your customers think.</strong></p><h3>Choose How to Use OpenRose</h3><p><strong>OpenRose</strong> can be deployed to support both menu creation and customer access. Your business can choose the setup that best fits its team, equipment and connectivity needs.</p><ul><li><strong>Editor for creating and managing menus:</strong> The full editor application connects to a backend database. Administrators and staff who manage the menu can use it to create and update menu content.</li><li><strong>Hosting for customer-facing menus:</strong> The digital menu can be hosted separately for customers to browse. It can be made available online through a cloud or web-hosting provider, or hosted offline within your restaurant, depending on your setup.</li></ul><p>These options give you flexibility over how your team works with menus and how customers access them. If you’re interested, try <strong>OpenRose</strong> with a small selection of dishes for a weekend or a week. Share the menu with staff and customers, gather their feedback, and see which setup works best for your business.</p><h3>Help Customers Choose with Confidence</h3><p>A digital menu can give customers more than a dish name and price. With <strong>OpenRose</strong>, you can add descriptions, photographs and useful indicators for allergens, spice levels and dietary choices, helping diners understand what’s on offer before they order. Clear, appealing information can make it easier for customers to find dishes that suit their tastes and needs — and help them feel more confident about their choices.</p><p>When common questions are answered right on the menu, staff may spend less time repeating basic details and more time welcoming guests and providing attentive service. A better-informed customer can have a smoother dining experience, which may encourage positive feedback and return visits. Menu information should still be kept accurate, and staff should be ready to help with questions — especially about allergens and dietary requirements.</p><h3>A More Flexible Alternative to Reprinting</h3><p>Printed menus can be useful, but updating them often means editing, reprinting and replacing copies. A digital menu can make changes easier to share and lets customers browse from their own device by scanning a QR code. Using a digital option can also reduce the need for printed copies, helping your business use less paper while showing customers that you’re considering more sustainable ways to share information.</p><h3>Make Room for What’s New on Your Menu</h3><ul><li><strong>Launch new dishes quickly:</strong> When your chef creates a new dish, add it to the digital menu without waiting to redesign and print paper menus. Customers can see what’s new as soon as you publish the update.</li><li><strong>Showcase guest-chef creations:</strong> Bringing in a guest chef for a weekend or a week? Give their special dish a place on your menu, with a photo and description that tell customers what makes it unique. When the chef’s visit ends, you can update the menu again.</li><li><strong>Celebrate your kitchen’s creativity:</strong> Chefs and kitchen teams may be excited to experiment beyond the regular menu. <strong>OpenRose</strong> makes it easier to present those fresh ideas as specials, giving customers something different to discover.</li><li><strong>Highlight seasonal and limited-time offerings:</strong> Feature festive dishes, special ingredients or short-run menu combinations while they’re available. A digital menu lets you update those offerings without printing a whole new batch of menus each time.</li></ul><h3>Make Quiet Hours an Opportunity</h3><p>Weekday afternoons and other quieter periods can be a great time to invite people in for something special. Your restaurant might offer an afternoon menu, a group deal, a tasting event or a hands-on cooking class. A dedicated digital menu makes it easy to present the event, its dishes and any special pricing in one clear place.</p><p>With <strong>OpenRose</strong>, you can prepare a menu for a particular day, time or occasion and share it with customers through a QR code or a link on your website. Update it when the event changes, promote a new experience, and give customers a fresh reason to visit — even during the quieter parts of the week.</p><h3>Understand What Customers Explore — and Help Them Discover More</h3><ul><li><strong>Understand how customers explore your menu:</strong> If your <strong>OpenRose</strong> setup includes analytics or compatible monitoring tools, you may be able to see which menu sections and dishes attract attention. These insights can help you understand what customers are interested in and guide future menu planning.</li><li><strong>Make more informed menu decisions:</strong> Engagement data can help you spot dishes worth featuring, sections that may need clearer descriptions, or ideas for themed and targeted menus. Treat menu views as a sign of interest — not proof that a dish was ordered — unless you also collect order data through a separate system.</li><li><strong>Give guests something to browse while they wait:</strong> After placing an order, customers can explore the rest of the menu on their phones. Clear descriptions and appealing photos can help them discover drinks, desserts or other dishes they might enjoy on a future visit.</li><li><strong>Make group dining easier to explore:</strong> When one person places an order for a family or group, others can browse the digital menu at their own pace. Having the menu readily available makes it easier for everyone to see what’s offered and consider additions for the table.</li><li><strong>Measure only what your setup supports:</strong> Interest in bookings or customer inquiries can be tracked only if your website or other connected tools record those interactions. Choose metrics that are useful to your business and handle any customer data appropriately.</li></ul><h3>One Menu, A Consistent Experience Across Every Location</h3><p>For a restaurant chain or growing food business, a shared digital menu can help keep the brand experience consistent from one branch to the next. <strong>OpenRose</strong> may offer a practical, open-source way to support that approach — particularly for emerging chains that want to manage their menus without immediately investing in a large, specialised IT platform. The exact process for distributing updates across locations will depend on how <strong>OpenRose</strong> is deployed.</p><ul><li><strong>Manage a shared menu centrally:</strong> A head office team can prepare the core menu — such as dish names, descriptions, images and dietary information — for use across the chain. This helps each location present the same dishes and brand story.</li><li><strong>Give customers a familiar experience:</strong> When customers visit different branches, a consistent digital menu can make it easier to recognise favourite dishes and explore the chain’s offerings, whether they’re at home or travelling.</li><li><strong>Make updates easier to coordinate:</strong> New dishes, seasonal menus or changes to descriptions can be prepared centrally and shared with participating branches through the chosen deployment setup. Locations can still have agreed local variations where needed.</li><li><strong>Support growth without unnecessary complexity:</strong> Startups and expanding restaurant groups may not have a large IT team or budget for specialised enterprise software. <strong>OpenRose</strong>’s open-source approach gives them an option to explore, with their own IT support or assistance from <strong>OpenRose</strong> for setup and hosting.</li><li><strong>Put menus where customers can find them:</strong> Publish the chain’s digital menu online and link to it from the company website, so customers can browse before choosing a branch to visit. For location-specific menus, the setup should make clear which menu applies to which restaurant.</li></ul><h3>Let special Ingredient Tell a Story</h3><p>Some dishes are special because of the ingredients behind them. If you use a distinctive pineapple from a particular region, a prized spice or another carefully sourced ingredient, tell customers what makes it worth discovering. With <strong>OpenRose</strong>, you can enrich a dish’s menu listing with details about its ingredients and origins, along with a photograph or a link to a video that brings the story to life.</p><p>That story gives guests something interesting to explore while their food is being prepared — and can help them feel more connected to the dish, the people who produce its ingredients and the places they come from. Clear, thoughtful sourcing information can add meaning to the dining experience and help customers appreciate the care behind what they’re about to enjoy. If you offer a way for guests to support producers directly, your menu can also point them to details about that initiative too.</p><h3>Go Beyond Reviews: Make Every Menu Visit More Meaningful</h3><ul><li><strong>Give guests useful details in the moment:</strong> A digital menu can bring dish descriptions, ingredient information, photos and sourcing stories together where customers are choosing what to eat. Guests can explore at their own pace without needing to search elsewhere.</li><li><strong>Add context that a star rating can’t convey:</strong> Public reviews can help people discover your restaurant, but they may not capture every detail of the dining experience — or tell you exactly what a guest wanted to know. A thoughtful menu lets you explain what makes a dish distinctive before it reaches the table.</li><li><strong>Complement review platforms, don’t rely on them alone:</strong> Online reviews and recommendations can support your restaurant’s visibility, while a well-presented digital menu helps shape the experience for customers already considering a visit. You can also invite guests to share feedback directly with your team, giving you another way to learn what they value.</li><li><strong>Give customers something worth sharing:</strong> A memorable dish, a clear story about its ingredients or a distinctive menu experience can give guests a reason to talk about your restaurant with friends, family or food bloggers. It won’t guarantee a review or a return visit, but it can help make the experience more engaging and memorable.</li><li><strong>Encourage discovery and repeat visits:</strong> When customers can easily browse specials, seasonal dishes and the stories behind them, they may find something new to try on their next visit. <strong>OpenRose</strong> helps you present that information through a digital menu that’s easy to access and update.</li></ul><h3>A Digital Menu Customers Can Take With Them</h3><ul><li><strong>Easy to open at the restaurant:</strong> Customers scan a QR code with their phone and view the menu in a web browser, without needing to download a separate app.</li><li><strong>Available beyond the visit:</strong> When your menu is hosted online, customers can keep its link and look at it again later — whether they’re planning another visit, sharing it with friends or deciding what to order next time.</li><li><strong>Focused on showing your menu:</strong> <strong>OpenRose</strong> is designed to present your dishes, descriptions, images and other menu information. It does not currently connect to ordering or payment systems, keeping its role straightforward: helping customers discover what your restaurant serves.</li><li><strong>Use it alongside your existing service:</strong> Because the digital menu doesn’t replace your ordering or payment process, you can offer it as another way for customers to browse while continuing to serve them through your usual methods.</li></ul><p>A simple online menu gives people an easy way to remember what you offer and find it again when they’re ready to visit. For restaurants that want a clear, shareable digital catalogue without adding an ordering or payment system, <strong>OpenRose</strong> keeps the experience focused.</p><h3>Make OpenRose Your Digital Menu</h3><p>From an independent café or food van to a growing restaurant group, <strong>OpenRose </strong>offers a simple way to bring your menu online. Customers can scan a QR code, browse dishes and drinks on their own devices, and explore the images, descriptions, dietary details and stories that make your food special. Your team can update menus for seasonal offers, new dishes and special events — without needing to redesign and reprint the whole menu each time.</p><p><strong>OpenRose </strong>is free and open source, giving food businesses a flexible way to create a digital menu without adopting a complex ordering or payment system. Use your own IT team or provider to set it up, or choose optional support for deployment, hosting and ongoing assistance. Give <strong>OpenRose </strong>a try with a sample menu, invite your customers and staff to explore it, and see how a clear, accessible digital menu could help your business share its food with the world.</p><p><strong>Ready to give your menu a digital home? Explore the OpenRose sample menu and see what’s possible.</strong></p><p><strong><em>OpenRose</em></strong><em>, a free and open-source application / tool. For more information, visit</em></p><h3><a href="https://github.com/openrose">https://github.com/openrose</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SH_Q7HcYlq70me5LD-A6kw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7d52562ef55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Actions Tab: Streamline Requirements Management]]></title>
            <link>https://medium.com/@openrose/actions-tab-streamline-requirements-management-79bf97e0589c?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/79bf97e0589c</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[user-stories]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 12:36:00 GMT</pubDate>
            <atom:updated>2026-10-08T12:36:00.582Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FodEnbUbX9WI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DodEnbUbX9WI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FodEnbUbX9WI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff77bf346859ec07b6668fba928fd35b/href">https://medium.com/media/ff77bf346859ec07b6668fba928fd35b/href</a></iframe><p>Imagine having every important command right where you need it: no searching through menus, no extra steps, no copying and pasting IDs, and no interruptions to your workflow.</p><p><strong>OpenRose </strong>now introduces the <strong>Actions</strong> tab across all record types, giving you fast, direct access to the commands you use most. Whether you’re working with a project, a requirement type, individual requirements, baselines, or other records, the Actions tab makes it easy to move, copy, import, and export data. You can also create Mermaid flowcharts and access other useful commands directly from the record you’re viewing.</p><p>The result is a smoother, more consistent experience across the entire tool. Let’s take a look at this new capability.</p><h3>Copying a Project</h3><p>I’m going to use the Charity Fundraising project, where I can see all my data in a tree view on the left-hand side.</p><p>When I open any record — whether it’s a project, an item type, or a requirement — we can see the Actions tab. It contains useful commands for that record.</p><p>For example, if I want to create a copy of the Charity Fundraising project, I can select <strong>Copy Project</strong>. Let me demonstrate. First, let’s go back to the project list. We only see Charity Fundraising. I’ll open the project, go to the Actions tab, and select <strong>Copy</strong>.</p><p>Notice that I don’t have to copy the ID or enter any of this data manually. It’s filled in automatically, and a new tab opens with the information already captured. We’re copying a project, so when I click <strong>Copy</strong>, the new copy is created.</p><p>I can close this tab because I don’t need it anymore. Back in the project list, I can now see both the original project and the copy. It’s as simple as that.</p><p>Let’s clean up by deleting the copy we just created. Now we’re back to the list, where only the original project appears.</p><h3>Actions for Requirement Types</h3><p>Let’s open the Charity Fundraising project again and explore the actions available for requirement types. Here, we can move a requirement type under a new project or between existing requirement types, copy it, export it as JSON, or create a Mermaid flowchart.</p><p>Let’s try creating a Mermaid flowchart. The ID shown here is automatically filled in on the flowchart export screen. Then I can choose what to include. For example, I can generate tree-view links, include tags, and add estimations if needed. When I’m ready, I generate the Mermaid flowchart text.</p><p>The code is generated automatically. I can copy it, open Mermaid, and use the code to plot the diagram. Here we can see the fundraising preparation requirement type and its requirements. Some of them include tags used for demonstration and testing.</p><p>The idea is that you can use the Actions tab instead of navigating through the menu options. In this example, there are five different actions available for a requirement type.</p><h3>Actions for Requirements</h3><p>Now let’s look at a requirement and its available actions. Again, there are five actions. You can move a requirement under an existing requirement or requirement type, move it between existing requirement records, copy it, export it as JSON along with its children, or generate a Mermaid flowchart.</p><p>These actions provide options that you could otherwise access through the menu bar. For example, when copying from the menu, you will have to manually select the project and item type, enter details, and provide IDs for different records as you move through the process.</p><p>Instead, you can select <strong>Copy Item</strong> from the Actions menu. The information is filled in for you, and you can complete the copy with a click of a button.</p><p>We’ll continue improving the available actions. This is the first version of the Actions tab, with commands we think will be especially useful now available directly from each record.</p><h3>Actions for Baselines</h3><p>There’s also a baseline for the Charity Fundraising project. When I open it in the tree view, we can see that the baseline contains requirement-type data as well as requirements data. A baseline is a snapshot of the data from a point in time.</p><p>When I open the Actions tab for a baseline requirement type, I see two options: export the data as a JSON file or generate a flowchart for that baseline requirement type.</p><p>The options for moving and copying for baseline requirement type aren’t available because baselines are read-only by nature.</p><p>To demonstrate this, I’ll open <strong>OpenRose </strong>in a separate tab, open the Charity Fundraising project, and select the Fundraising Preparation requirement type. In the live project, I have five actions available. For the same requirement type inside the baseline — a read-only snapshot — I don’t see the move and copy actions.</p><p>The same applies to individual requirements. A baseline requirement is read-only. I can include or exclude it from the baseline, which affects the project’s overall estimation, but the Actions tab only lets me export it as a JSON data file or generate a Mermaid flowchart.</p><p>In the live project, I can move or copy the requirement, create multiple copies, export it, or generate a flowchart.</p><h3>Make Requirements Management Simpler with OpenRose</h3><p>That’s an overview of the new Actions tab. With this feature, <strong>OpenRose </strong>makes requirements management simpler, faster, and more intuitive.</p><p><strong>OpenRose </strong>is a <strong>free and open-source requirements management tool</strong>, accessible to everyone. Explore the new Actions tab, simplify your workflow, and discover what <strong>OpenRose </strong>can do for your projects.</p><p>Thank you for your time. We hope you’ll share <strong>OpenRose </strong>with others and with your teams. Please consider contributing to this community-driven, open-source requirements management tool.</p><p>Once again, thank you, and have a great day. Bye-bye.</p><blockquote><strong>OpenRose</strong>, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRA0VYTp3rhKWnotDLN_ng.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79bf97e0589c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements Traceability Show Hide Properties in ReadOnly Views]]></title>
            <link>https://medium.com/@openrose/requirements-traceability-show-hide-properties-in-readonly-views-c66f92b02a95?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c66f92b02a95</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[traceability]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 16:14:20 GMT</pubDate>
            <atom:updated>2026-10-02T16:14:20.588Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxPiOs54IoTY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxPiOs54IoTY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxPiOs54IoTY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c80c49480ea4494d49d9af1ba9ba38b/href">https://medium.com/media/8c80c49480ea4494d49d9af1ba9ba38b/href</a></iframe><p>Learn how <strong>OpenRose </strong>lets users show or hide status, priority, severity, and other requirement properties in read-only views and traceability data.</p><p>When presenting requirements to reviewers, customers, auditors, or other stakeholders, showing every internal property can sometimes create unnecessary complexity. Fields such as status, priority, severity, identifiers, and other administrative information may be important to project teams, but they are not always needed by everyone viewing the requirements.</p><p><strong>OpenRose </strong>introduces a simple way to control how requirement information appears in read-only views. With a single user setting, users can choose whether requirement properties should be visible or hidden. The setting creates a cleaner presentation without changing the underlying requirements data.</p><p>When properties are hidden, they are removed not only from individual requirement records but also from related traceability information. This includes parent and child requirement relationships displayed in traceability views. As a result, reviewers can focus on the requirement content, structure, and relationships without being overwhelmed by internal project details.</p><p><strong>OpenRose </strong>is a free and open-source requirements management tool designed to help individuals and teams define, organize, maintain, share, and report on requirements and related information. This new capability makes the platform more flexible for both internal project work and external requirements publishing.</p><h3>A Cleaner Way to Present Requirements</h3><p>Requirements often contain more information than a stakeholder needs to see during a review. A single record may include:</p><ul><li>Requirement ID</li><li>Title and description</li><li>Status</li><li>Priority</li><li>Severity</li><li>Tags</li><li>Traceability information</li><li>Parent and child relationships</li><li>Additional project-specific properties</li></ul><p>All of this information can be useful during development and analysis. However, displaying every field at once may make a review screen feel crowded. Reviewers may spend more time interpreting internal metadata than understanding the actual requirement.</p><p>The new property visibility control helps address this problem. Users can select a focused read-only presentation in which only the core requirement information is shown. The requirement name, description, traceability labels, and relationships remain available, while selected properties such as status, priority, and severity can be hidden.</p><p>This gives teams a more effective way to present requirements to different audiences.</p><h3>Show or Hide Properties with a Personal View Setting</h3><p>The feature is controlled through the user’s view settings. In the <strong>OpenRose </strong>application, users can access their personal view settings and enable or disable the option to show properties in read-only views.</p><p>The setting provides two presentation modes:</p><h3>Properties hidden</h3><p>In the default focused view, requirement properties are not displayed. Users can still see the core record information and navigate through the requirement structure, but fields such as status, priority, and severity are omitted.</p><p>This view is useful when the goal is to present the essential requirements without exposing internal project metadata.</p><h3>Properties shown</h3><p>When the setting is enabled, the additional fields become visible on requirement records. The same information is also displayed in the related traceability view.</p><p>This view is useful for project teams, analysts, administrators, and reviewers who need a more complete understanding of the current requirement state.</p><p>The setting can be changed whenever necessary. Users can switch between a simplified presentation and a detailed presentation without changing the stored requirement data.</p><h3>Traceability Information Becomes Easier to Read</h3><p>Traceability is one of the most important capabilities in a requirements management system. It allows users to understand how requirements relate to one another and how information flows through a project structure.</p><p>In <strong>OpenRose</strong>, a requirement may have upstream and downstream relationships. A user can follow a requirement to related parent or child records and continue navigating through additional levels of traceability.</p><p>When properties are visible, the traceability view may include fields such as:</p><ul><li>Requirement ID</li><li>Status</li><li>Priority</li><li>Severity</li><li>Traceability label</li><li>Requirement name</li><li>Parent or child relationship information</li></ul><p>This detailed view is valuable when performing analysis, impact assessment, or project control. However, it may be more information than a stakeholder needs during a simple requirements review.</p><p>With the new property visibility control, users can hide the additional fields from traceability records. The traceability view then focuses on the requirement names and relationships rather than displaying every property associated with each record.</p><p>This makes it easier to understand:</p><ul><li>Which requirements are connected</li><li>Which records are parents or children</li><li>How information flows between requirements</li><li>What the overall requirement structure looks like</li><li>Where to navigate next in the hierarchy</li></ul><p>The relationships remain available, but the presentation becomes less distracting.</p><h3>Supporting Different Requirements Management Audiences</h3><p>Different users need different levels of detail. A requirements engineer may need to see every property, while a business stakeholder may only need to review the requirement wording and its relationship to other requirements.</p><p>The same project may be viewed by:</p><ul><li>Requirements engineers</li><li>Software developers</li><li>Test engineers</li><li>Project managers</li><li>Product owners</li><li>Customers</li><li>Auditors</li><li>Suppliers</li><li>Business stakeholders</li><li>General users of a published requirements catalog</li></ul><p>Showing the same amount of information to every audience is not always the best approach. <strong>OpenRose</strong> allows users to choose a suitable read-only presentation based on the purpose of the review.</p><p>For example, an engineering team may enable properties to investigate priority and status. A customer-facing review may use the simplified view to focus on the requirements themselves. An auditor may choose the detailed view when examining the state of a baseline or a controlled set of requirements.</p><p>This flexibility supports both internal analysis and external communication.</p><h3>Read-Only Views for Live Repository Data</h3><p><strong>OpenRose </strong>can present requirements from a live repository in a read-only view. In this scenario, users can browse project information without modifying the underlying data.</p><p>The read-only view allows users to:</p><ul><li>Navigate through projects</li><li>Open requirement records</li><li>Review descriptions</li><li>Follow traceability links</li><li>Inspect parent and child records</li><li>View the project structure</li><li>Choose whether properties are shown</li></ul><p>The property visibility setting works in this read-only environment. A user can browse the live project while displaying either a simplified or detailed version of the requirements.</p><p>This is useful when an organization wants to give reviewers access to current information while preventing them from changing the source repository.</p><p>The result is a controlled viewing experience that supports review and collaboration without turning every user into an editor.</p><h3>Read-Only Views from Exported JSON Data</h3><p><strong>OpenRose </strong>also supports exporting project information into a JSON data file. The exported data can be used in a separate read-only environment, either through a server-hosted setup or through a client-facing JSON data file.</p><p>This creates a useful separation between:</p><ul><li>The live requirements repository used by the project team</li><li>A published read-only view used by reviewers and stakeholders</li></ul><p>A project administrator can export a project and make the resulting data available through a separate <strong>OpenRose </strong>instance. Users accessing that instance can browse the published requirements, but they do not connect directly to the SQL Server repository and cannot modify the source project.</p><p>This approach can be used to publish:</p><ul><li>Project specifications</li><li>Requirement catalogs</li><li>Customer-facing documentation</li><li>Review packages</li><li>Audit information</li><li>Product documentation</li><li>Approved project snapshots</li><li>Baseline-related data</li></ul><p>The property visibility setting gives viewers control over how much information they want to see in that read-only environment.</p><h3>Separating Internal Data from Published Information</h3><p>A requirements repository often contains information intended for internal use. Status values, priority classifications, severity ratings, and administrative fields may reflect internal decisions or work-in-progress information.</p><p>Not every field should necessarily appear in a public or stakeholder-facing catalog.</p><p><strong>OpenRose’s </strong>read-only presentation controls help organizations create a cleaner published view while preserving the underlying data in the source project. The same exported requirement content can be presented in a more focused way, without requiring the team to delete properties or create a second manually maintained document.</p><p>This can help reduce duplicated work. Instead of manually copying requirements into another format and removing internal fields, users can use the read-only view settings to control the presentation.</p><p>The original data remains available for authorized users who need a detailed view.</p><h3>Example: Stock Trading Platform Project</h3><p>The capability can be demonstrated using a project such as a stock trading platform. A project of this type may contain a large number of requirements and extensive traceability relationships.</p><p>Each requirement may have:</p><ul><li>A unique identifier</li><li>A title</li><li>A detailed description</li><li>A status</li><li>A priority</li><li>A severity</li><li>Related upstream requirements</li><li>Related downstream requirements</li><li>Traceability labels</li></ul><p>In the detailed view, users can see the properties directly on the requirement and within the traceability grid. This is valuable for project analysis because it provides context about the state and importance of each record.</p><p>In the simplified view, the properties are hidden. The user can still see the requirement and navigate through its relationships, but the screen concentrates on the core content and structure.</p><p>This makes the project easier to present to people who do not need to know the internal status or classification of every requirement.</p><h3>A Practical Workflow for Publishing Requirements</h3><p>A typical <strong>OpenRose </strong>publishing workflow may look like this:</p><ol><li>Maintain requirements in the live repository.</li><li>Review and organize the project structure.</li><li>Create or update traceability relationships.</li><li>Export the project as JSON data.</li><li>Host the exported data in a separate read-only <strong>OpenRose </strong>instance.</li><li>Provide access to reviewers or stakeholders.</li><li>Allow users to show or hide properties through their view settings.</li><li>Use the simplified view for focused reviews or demonstrations.</li><li>Enable the detailed view when additional project information is required.</li></ol><p>This workflow helps teams provide access to useful requirements information without giving every viewer direct access to the editable repository.</p><h3>Baselines and Requirement Snapshots</h3><p>The property visibility capability also applies to baseline-related data. In OpenRose, a baseline can be used as a snapshot of requirements captured at a particular point in time.</p><p>Baselines are useful for:</p><ul><li>Preserving an approved set of requirements</li><li>Capturing a release-specific scope</li><li>Supporting audits</li><li>Comparing changes over time</li><li>Recording a project decision</li><li>Reviewing historical requirement information</li><li>Establishing a controlled reference point</li></ul><p>A baseline may contain the same types of requirement properties and traceability relationships as live project data. When a baseline is displayed in a read-only view, users can apply the same presentation choice: show the detailed properties or hide them for a cleaner review.</p><p>This is particularly useful during audits and stakeholder approvals. An auditor may need to see the full status and priority information, while a business reviewer may only need to confirm that the requirement content and relationships are correct.</p><h3>Benefits of Hiding Requirement Properties</h3><p>The simplified read-only view provides several practical benefits:</p><ul><li>Reduces visual clutter.</li><li>Makes requirements easier to read.</li><li>Helps reviewers focus on requirement content.</li><li>Avoids overwhelming nontechnical stakeholders.</li><li>Creates a cleaner presentation for demonstrations.</li><li>Keeps internal fields out of stakeholder-facing views.</li><li>Makes traceability relationships easier to understand.</li><li>Supports customer and supplier reviews.</li><li>Provides a more approachable published catalog.</li><li>Reduces the need to manually create separate documentation.</li><li>Helps users concentrate on parent and child relationships.</li><li>Supports controlled presentation of live and exported data.</li></ul><h3>Benefits of Showing Requirement Properties</h3><p>The detailed view remains important for users who need deeper project information. Showing properties can help with:</p><ul><li>Requirement analysis</li><li>Impact assessment</li><li>Prioritization</li><li>Status reviews</li><li>Severity evaluation</li><li>Project planning</li><li>Change management</li><li>Traceability analysis</li><li>Baseline inspection</li><li>Audit preparation</li><li>Internal quality reviews</li></ul><p>The important point is that <strong>OpenRose </strong>does not force users to choose one permanent presentation style. The setting can be changed according to the task and audience.</p><h3>Why This Is Important for Open-Source Requirements Management</h3><p>Open-source requirements management tools need to support both technical users and occasional reviewers. A requirements engineer may work with detailed metadata every day, while a stakeholder may access the system only during a monthly review.</p><p>A flexible presentation layer helps serve both groups without making the application unnecessarily complicated.</p><p><strong>OpenRose </strong>combines structured requirements, hierarchical organization, traceability, baselines, JSON export, and read-only views in a platform designed for individuals and teams. Its property visibility control adds another layer of flexibility by allowing users to decide how much information appears during a review.</p><h3>Simple, Focused, and User-Controlled</h3><p>The new setting is intentionally simple. Users do not need to change the project structure, remove fields, modify the database, or produce a separate document. They can use the personal view setting to switch between a detailed and simplified read-only experience.</p><p>This makes the feature practical for everyday work:</p><ul><li>Need detailed project information? Show the properties.</li><li>Preparing a stakeholder review? Hide the properties.</li><li>Reviewing traceability? Choose the level of detail that fits the task.</li><li>Publishing a requirements catalog? Use a focused view.</li><li>Inspecting a baseline? Enable the fields needed for the audit.</li></ul><p>The information remains available, but users are given control over how it is presented.</p><h3>Final Thoughts</h3><p><strong>OpenRose’s </strong>property visibility control improves the way requirements are presented in read-only views. By allowing users to show or hide status, priority, severity, and other properties, the feature creates a more adaptable experience for requirements reviews, stakeholder demonstrations, audits, and published project catalogs.</p><p>When properties are hidden, the simplified presentation applies not only to individual requirements but also to their traceability records. Parent and child relationships remain visible, while unnecessary metadata is removed from the viewing experience.</p><p>When properties are shown, users can access the detailed information required for engineering analysis, project management, impact assessment, and audit activities.</p><p>This balance between detail and simplicity makes <strong>OpenRose </strong>more useful for different audiences and different requirements management scenarios. Whether the data comes from a live repository, an exported JSON file, a hosted read-only project, or a baseline snapshot, users can choose the view that best matches their needs.</p><p><strong>OpenRose </strong>continues to provide a flexible, free, and open-source way to manage and share structured requirements. This latest capability helps teams present their requirements more clearly, keep reviewers focused, and make traceability information easier to understand.</p><blockquote><strong>OpenRose</strong>, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtOHM-cYgIg3YCeHwVaDHg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c66f92b02a95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Screen Toggle Button — A More Focused Way to View Requirements]]></title>
            <link>https://medium.com/@openrose/full-screen-toggle-button-a-more-focused-way-to-view-requirements-91ec797c8e14?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/91ec797c8e14</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[traceability]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 15:04:18 GMT</pubDate>
            <atom:updated>2026-10-02T15:04:18.732Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fq7-QzfiH51U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dq7-QzfiH51U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fq7-QzfiH51U%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/24e5a552ef9da98c620b822c9ae4c840/href">https://medium.com/media/24e5a552ef9da98c620b822c9ae4c840/href</a></iframe><p>Discover how the new full-screen toggle in OpenRose improves requirements management on desktop, mobile, read-only views, and editing screens.</p><p>OpenRose is a free and open-source requirements management tool designed to help individuals and teams define, organize, maintain, share, and report on requirements and related project information. With its latest user-interface improvements, OpenRose makes it easier to focus on the information that matters most. One of these improvements is the new <strong>full-screen toggle button</strong>, which allows users to quickly expand the details area, hide the navigation tree, and return to the standard split-screen layout whenever needed.</p><p>This capability is especially useful for users working with large projects, detailed requirements, traceability information, specifications, catalogs, and other structured data. Instead of manually adjusting the split bar between the tree view and the detail view, users can now switch between layouts with a single button.</p><h3>What Is the OpenRose Full-Screen Toggle?</h3><p>The OpenRose interface commonly uses a two-panel layout:</p><ul><li>A tree view on the left for navigating projects, requirements, and other records.</li><li>A detail view on the right for displaying the selected record.</li><li>A split bar between the two areas for manually adjusting the available screen space.</li></ul><p>The new full-screen toggle provides a faster alternative to manually moving the split bar. When users select the toggle button, the detail view expands to use the available width. This creates a cleaner, more focused workspace for reading, reviewing, or editing a selected record.</p><p>Users can then select the toggle again to restore the normal layout and bring the tree view back into view.</p><p>This simple interaction gives users control over how they want to work. The standard view is useful when navigating between records, while the full-screen view is ideal when concentrating on a specific requirement or project detail.</p><h3>A Better Way to Review Project Information</h3><p>In a typical OpenRose project, users may need to move through several levels of information. For example, they might open a project, select a requirement group, choose a specific requirement, and then review its title, description, status, priority, severity, tags, or traceability information.</p><p>The split-screen layout provides useful context because the navigation tree remains visible. However, the available space for the details panel can become limited, particularly when the selected record contains a long description or a large amount of information.</p><p>The full-screen toggle solves this problem by allowing the selected record to occupy the main viewing area. Users can focus on the information without being distracted by the navigation panel or repeatedly resizing the split bar.</p><p>The feature is useful for:</p><ul><li>Reviewing detailed requirements</li><li>Reading long descriptions</li><li>Inspecting project information</li><li>Presenting specifications to colleagues</li><li>Reviewing traceability data</li><li>Examining baseline content</li><li>Viewing published or server-hosted project data</li><li>Working with large requirement catalogs</li></ul><h3>Full-Screen Mode in Read-Only Views</h3><p>OpenRose supports read-only views for projects and data hosted through exported files or server-based deployments. These views are useful when users need to publish or share requirements information without allowing changes to the underlying repository.</p><p>In a read-only tree view, users can navigate through the project structure and select individual records. The full-screen toggle works in this environment as well. When activated, it expands the selected record’s details so that the information can be viewed across the available screen width.</p><p>This creates a more comfortable experience for people who are reviewing requirements but do not need editing access. For example, a customer, auditor, project manager, tester, or stakeholder may want to inspect a requirement without needing the complete editing interface.</p><p>The full-screen read-only experience is particularly valuable for:</p><ul><li>Requirements reviews</li><li>Project demonstrations</li><li>Stakeholder presentations</li><li>Published specifications</li><li>Baseline inspections</li><li>Audit activities</li><li>Shared project documentation</li><li>Web-based requirements portals</li></ul><p>Users can switch back to the regular layout whenever they need to navigate to another record.</p><h3>Full-Screen Mode While Editing Requirements</h3><p>The same layout improvement is available when working in the editable OpenRose application connected to a repository. In this mode, users can update project and requirement information, including fields such as:</p><ul><li>Title</li><li>Description</li><li>Status</li><li>Priority</li><li>Severity</li><li>Requirement properties</li><li>Traceability information</li><li>Other record-specific details</li></ul><p>The full-screen toggle gives the editor more room to work with the selected record. This is especially helpful when entering or reviewing a detailed description, checking multiple fields, or working with content that requires more horizontal space.</p><p>Rather than constantly resizing the navigation panel, users can temporarily hide it, complete their work, and restore it when they are ready to navigate elsewhere.</p><p>This makes the feature useful throughout the complete requirements workflow — from creating and editing a requirement to reviewing and publishing it.</p><h3>A Separate Full-Screen Option for Descriptions</h3><p>OpenRose also provides a full-screen option within the description editor. This is a separate level of full-screen functionality.</p><p>The application-level full-screen toggle expands the selected record and changes the relationship between the tree view and the detail view. The description editor’s full-screen option goes one step further by focusing specifically on the description content.</p><p>When users activate full-screen mode inside the description component, the description becomes the primary visible area. This is useful when writing or reviewing Markdown and HTML-based content.</p><p>The description-focused view can help users:</p><ul><li>Write long requirement descriptions</li><li>Review formatted content</li><li>Edit Markdown</li><li>Inspect HTML output</li><li>Focus on the wording of a specification</li><li>Reduce visual distractions while editing</li></ul><p>Pressing the <strong>Escape</strong> key returns the description editor to its normal size. Users can then continue working within the OpenRose interface or use the main full-screen toggle to restore the broader application layout.</p><h3>Designed for Smaller Screens and Mobile Devices</h3><p>One of the most important benefits of the full-screen toggle is improved usability on smaller devices. On a desktop monitor, users may have enough room to display both the navigation tree and the details panel. On a mobile phone or smaller touchscreen, the same two-panel layout can feel crowded.</p><p>OpenRose addresses this by prioritizing the details area when the application is first opened on a small screen. Instead of immediately displaying the tree view beside the record details, the application can use the available width to show the selected information more clearly.</p><p>Users can then open the tree view when they need to navigate to another record. This approach provides a more practical mobile workflow:</p><ol><li>Open the project or hosted data.</li><li>View the selected record using the available screen width.</li><li>Open the tree view when navigation is required.</li><li>Select another record.</li><li>Return to the focused details view.</li></ol><p>This interaction is more comfortable for touchscreen users because it reduces the need to drag a narrow split bar with a finger. A dedicated button is easier to locate and use than a small divider between panels.</p><h3>Responsive Behavior in Portrait and Landscape Orientations</h3><p>The full-screen toggle also supports different device orientations. On a mobile phone in landscape mode, the application may have more horizontal space for displaying the tree and details together. In portrait mode, the vertical layout may provide a better view of the project structure and selected record.</p><p>The interface adjusts to the available dimensions, allowing users to choose the layout that works best for their device and task.</p><p>This responsive behavior helps OpenRose support a wide range of working environments, including:</p><ul><li>Desktop computers</li><li>Laptops</li><li>Tablets</li><li>Touchscreen devices</li><li>Mobile phones</li><li>Embedded browser windows</li><li>Server-hosted read-only views</li></ul><p>The goal is not simply to make the application smaller on a mobile screen. It is to make the information easier to use regardless of the device being used.</p><h3>How the Full-Screen Toggle Works</h3><p>The feature is designed to be simple and requires no complicated configuration.</p><h3>To expand the selected record</h3><ol><li>Open an OpenRose project or hosted data view.</li><li>Navigate to a project, requirement, baseline, or other record.</li><li>Select the full-screen or toggle split-bar button.</li><li>The details view expands and the navigation tree is hidden or reduced.</li></ol><h3>To restore the standard layout</h3><ol><li>Select the toggle button again.</li><li>The tree view returns to the left side.</li><li>The details view returns to the standard split-screen layout.</li><li>Continue navigating through the project as usual.</li></ol><p>When working inside the description editor, users can use the editor’s own full-screen control. Pressing <strong>Escape</strong> returns the description to its normal editing view.</p><h3>Making Better Use of Screen Space</h3><p>OpenRose uses a balanced split-screen layout for normal operation. A portion of the available width is allocated to the navigation tree, while the remaining space is used for the selected record.</p><p>This arrangement is useful for navigation because users can see the project hierarchy and the current record at the same time. However, it is not always ideal for reading long descriptions or reviewing detailed content.</p><p>The full-screen toggle allows users to change the layout based on their immediate task:</p><ul><li>Use the standard layout when navigating.</li><li>Use the expanded layout when reading.</li><li>Use the editor full-screen view when writing detailed content.</li><li>Restore the tree view when moving to another record.</li></ul><p>This task-based approach makes the interface more flexible without adding unnecessary menus or configuration screens.</p><h3>Why This Matters for Requirements Management</h3><p>Requirements management often involves reviewing information from different perspectives. A project manager may need to browse the hierarchy. A business analyst may need to read and refine a requirement. A tester may want to inspect acceptance criteria. An auditor may need to review a published baseline. A stakeholder may simply need a clear view of the final specification.</p><p>Each of these activities benefits from a different amount of screen space.</p><p>The full-screen toggle improves OpenRose by allowing users to change the interface without changing the underlying project data. It does not remove the navigation tree or permanently alter the application. Instead, it provides a quick way to move between context and focus.</p><p>That makes the feature useful for both casual users and people who work with OpenRose throughout the day.</p><h3>Key Benefits of the OpenRose Full-Screen Feature</h3><ul><li>Provides one-click access to an expanded details view.</li><li>Reduces the need to manually drag the split bar.</li><li>Makes long requirements easier to read.</li><li>Creates more workspace for editing descriptions.</li><li>Improves usability on mobile phones and tablets.</li><li>Supports both editable and read-only project views.</li><li>Makes presentations and demonstrations easier.</li><li>Helps users focus on one record at a time.</li><li>Allows users to restore the navigation tree whenever required.</li><li>Works with project, requirement, baseline, and other record-oriented views.</li><li>Supports responsive layouts across different screen sizes and orientations.</li><li>Provides a separate focused view for Markdown and HTML descriptions.</li></ul><h3>OpenRose: Free and Open-Source Requirements Management</h3><p>OpenRose is built as an open-source requirements management application for individuals and teams. Its purpose is to make it easier to define, organize, maintain, share, and report on requirements and related information.</p><p>The platform can be used for many types of structured content, including:</p><ul><li>Software requirements</li><li>Product specifications</li><li>Project documentation</li><li>Needs and wants</li><li>Activities and action lists</li><li>Test-related information</li><li>Research findings</li><li>Rules and procedures</li><li>Contract specifications</li><li>Traceability records</li><li>Baselines and requirement catalogs</li></ul><p>Because OpenRose is free and open source, organizations and individuals can explore the tool without the licensing cost associated with many commercial requirements management platforms. The community-driven approach also creates opportunities for users and contributors to suggest improvements, test new capabilities, and help shape the future of the application.</p><h3>Final Thoughts</h3><p>The new full-screen toggle button is a small interface improvement with a significant effect on everyday usability. It gives OpenRose users a faster way to move between navigation and focused content views, whether they are working on a desktop computer, tablet, or mobile device.</p><p>For users who need to review detailed requirements, edit descriptions, inspect read-only project data, or present specifications to others, the feature provides more space and fewer distractions. The ability to restore the tree view with the same control ensures that users can quickly return to navigation whenever needed.</p><p>Together with its responsive layout, read-only views, editable repository connections, and structured requirements features, the full-screen toggle makes OpenRose a more adaptable open-source requirements management tool.</p><p>Explore the latest OpenRose capabilities, try the full-screen toggle in your project views, and share the project with others who are looking for a flexible and free way to manage requirements.</p><blockquote>OpenRose, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sDPxTXeOba6FFMI784HuKg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91ec797c8e14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mermaid Diagrams With Requirement TreeView Links]]></title>
            <link>https://medium.com/@openrose/mermaid-diagrams-with-requirement-treeview-links-ded098e671ec?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ded098e671ec</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[requirements-engineering]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Wed, 23 Sep 2026 17:50:00 GMT</pubDate>
            <atom:updated>2026-09-23T17:50:00.824Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCcY-6rS_7YY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCcY-6rS_7YY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCcY-6rS_7YY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2f1083b2c576b4f05fa53372b8f4c11/href">https://medium.com/media/c2f1083b2c576b4f05fa53372b8f4c11/href</a></iframe><p><strong>OpenRose </strong>now allows users to click any node inside an exported Mermaid flowchart and jump <em>directly</em> into the <strong>TreeView</strong>, giving instant access to the full project hierarchy without navigating through individual detail pages. This upgrade makes Mermaid diagrams interactive, intuitive, and far more useful for real‑world requirements work.</p><h3>What This New Feature Does</h3><p>OpenRose has always provided two core navigation modes:</p><ul><li><strong>TreeView</strong> — a complete hierarchical view of your project</li><li><strong>Detail View</strong> — focused, one‑record‑at‑a‑time inspection</li></ul><p>TreeView is where users get the full picture: expandable nodes, relationships, and the ability to edit requirements in context. But until now, Mermaid diagrams exported from OpenRose always linked back to the <strong>Detail View</strong>. That meant extra clicks and breadcrumb navigation.</p><p>With <strong>TreeView URL links enabled</strong>, every node in your Mermaid diagram becomes a direct jump into the TreeView. Users can click a requirement and instantly see:</p><ul><li>where it sits in the hierarchy</li><li>its parent and sibling items</li><li>all related sub‑requirements</li><li>the full project context</li></ul><p>This makes Mermaid diagrams not just visual summaries, but <strong>interactive navigation tools</strong>.</p><h3>How It Works</h3><p>When exporting a Mermaid flowchart, you now have an additional option:</p><ul><li><strong>Generate TreeView URL Links</strong></li></ul><p>If enabled, OpenRose adds a small parameter to each link in the Mermaid output. That parameter tells OpenRose to open the clicked requirement in <strong>TreeView</strong> instead of Detail View.</p><p>If disabled, links behave the traditional way and open the Detail View.</p><p>This gives users full control depending on how they want to present or explore their project.</p><h3>Example: Mountain Trekking Project</h3><p>Imagine a project with mountains from Europe, Africa, North America, South America, and Asia. The Asian section includes detailed planning information such as:</p><ul><li>visa requirements</li><li>equipment lists</li><li>accommodation details</li><li>safety considerations</li></ul><p>If you export only the <strong>Asia → Everest Base Camp</strong> section into a Mermaid diagram, you still get full navigation. Clicking any node — even though it came from a partial export — takes you to the correct place in TreeView.</p><p>OpenRose automatically understands:</p><ul><li>which project the requirement belongs to</li><li>where it sits in the hierarchy</li><li>how to open it in TreeView</li></ul><p>This works without exporting the entire project. You can export a small subset, and TreeView navigation still functions perfectly.</p><h3>Why This Matters</h3><p>This upgrade delivers several practical benefits:</p><ul><li><strong>Faster navigation</strong> — no more breadcrumb clicking</li><li><strong>Better clarity</strong> — TreeView shows the full context instantly</li><li><strong>Improved collaboration</strong> — stakeholders can explore the project structure easily</li><li><strong>Smarter presentations</strong> — Mermaid diagrams become interactive gateways</li><li><strong>Consistent workflow</strong> — TreeView remains the central place for editing and reviewing</li><li><strong>Partial exports still work</strong> — even small diagrams link back to the full project</li></ul><p>For teams working with large requirement sets, this is a major usability improvement.</p><h3>Ideal for Management and Stakeholder Reviews</h3><p>Mermaid diagrams are often used to present high‑level summaries. With TreeView links:</p><ul><li>managers can click any node</li><li>instantly see related requirements</li><li>understand scope and dependencies</li><li>explore the project without needing guidance</li></ul><p>This bridges the gap between <strong>visual summaries</strong> and <strong>deep project insight</strong>, making reviews smoother and more productive.</p><h3>Summary</h3><p>This blog post helps users searching for:</p><ul><li>requirements management tools with Mermaid diagram support</li><li>TreeView navigation in requirements software</li><li>interactive flowchart‑based requirements exploration</li><li>open‑source requirements management platforms</li><li>visual traceability and project mapping tools</li></ul><p>OpenRose now stands out as a free, open‑source solution that supports <strong>TreeView navigation directly from Mermaid flowcharts</strong>, making it easier to explore, review, and manage complex projects.</p><h3>Conclusion</h3><p>The new TreeView link option transforms Mermaid diagrams from static visuals into powerful, interactive navigation tools. Whether you’re presenting to management, reviewing requirements with your team, or exploring a complex project, this feature makes OpenRose faster, smarter, and more intuitive.</p><p>OpenRose continues to grow through community contributions — documentation, testing, enhancements, and real‑world usage. This update is another step toward making OpenRose the most accessible and capable open‑source requirements management platform available today.</p><blockquote>OpenRose, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQLDl8aMWqgxttBUBT9JFQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ded098e671ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AppSettings Overrides in OpenRose: A Complete Guide for Administrators]]></title>
            <link>https://medium.com/@openrose/appsettings-overrides-in-openrose-a-complete-guide-for-administrators-6870386af1d9?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6870386af1d9</guid>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[application-configuration]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[environment-variables]]></category>
            <category><![CDATA[business-analyst]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 10:35:15 GMT</pubDate>
            <atom:updated>2026-09-07T10:35:15.639Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTDtwCJSBAC8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTDtwCJSBAC8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTDtwCJSBAC8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6e28b7829e07cf16a06622ebbac1577a/href">https://medium.com/media/6e28b7829e07cf16a06622ebbac1577a/href</a></iframe><p><strong>OpenRose</strong> requirements management tool has introduced a major upgrade to its configuration system — one that dramatically improves how administrators deploy, secure, and manage the application across different environments. This blog post is written specifically for users who install OpenRose themselves and for administrators responsible for configuring OpenRose for teams. It explains how AppSettings Overrides work, why they matter, and how you can use them to control OpenRose’s startup modes without ever touching <em>appsettings.json</em>.</p><h3>What AppSettings Overrides Solve</h3><p><strong>Takeaway:</strong> OpenRose now supports overriding configuration values through <strong>environment variables</strong> and <strong>command‑line parameters</strong>, eliminating the need to manually edit <em>appsettings.json</em>.</p><p>Historically, administrators had to:</p><ul><li>Access the server’s file system</li><li>Open <em>appsettings.json</em></li><li>Modify values directly</li><li>Restart the application</li></ul><p>This approach becomes difficult or impossible in:</p><ul><li>Locked‑down enterprise environments</li><li>Cloud deployments where file access is restricted</li><li>Automated CI/CD pipelines</li><li>Containerized environments (Docker, Kubernetes)</li></ul><p>OpenRose now embraces the full .NET configuration hierarchy:</p><ol><li><strong>AppSettings.json</strong></li><li><strong>Environment Variables</strong></li><li><strong>Command‑Line Parameters</strong></li></ol><p>This means you can override any setting — even disable entire subsystems — without modifying the underlying JSON file.</p><h3>The Three Startup Modes in OpenRose</h3><p>OpenRose supports three distinct modes of operation. AppSettings Overrides allow administrators to switch between them instantly.</p><h3>1. Client Data File Mode (Lightweight Read‑Only)</h3><p>Users can upload a JSON file exported from OpenRose and view it in the Web UI.</p><p>Ideal for:</p><ul><li>Simple deployments</li><li>Environments without an API server</li><li>Read‑only access to shared project data</li></ul><h3>2. Server Data File Mode (Hosted JSON Files)</h3><p>Administrators can host exported JSON files on the server.<br>Users can browse these files directly from the Web UI.</p><p>Useful when:</p><ul><li>You want to publish read‑only project snapshots</li><li>You don’t want to expose the API server</li><li>You need a secure, minimal deployment</li></ul><h3>3. Full Server‑Connected Mode (Web UI + API + SQL Server)</h3><p>The Web UI connects to the API server, enabling:</p><ul><li>Editing projects</li><li>Creating new projects</li><li>Full requirements management workflow</li></ul><p>This is the complete OpenRose experience.</p><p>If you want to explore how OpenRose handles hosted JSON files and static media, you can learn more about <strong>static file hosting</strong>.</p><h3>Demonstrating AppSettings Overrides in Action</h3><p>The video transcript walks through all three modes and shows how OpenRose reacts to configuration changes.</p><h3>Starting in Full Server‑Connected Mode</h3><p>Initially:</p><ul><li>The API server is running</li><li>The Web UI connects to the API</li><li>Projects are editable</li><li>Server‑hosted JSON files are visible</li><li>Client JSON files can be opened</li></ul><p>This is the default behavior when <em>appsettings.json</em> contains valid API and offline folder settings.</p><h3>Disabling API Connectivity Using Environment Variables</h3><p>Instead of editing <em>appsettings.json</em>, the administrator sets:</p><pre>APISettings__BaseUrl=&quot;&quot;</pre><p>This environment variable overrides the JSON value and sets the API base URL to <em>null</em>.</p><p>After restarting the Web UI:</p><ul><li>The API server is still running</li><li>The Web UI refuses to connect to it</li><li>Editing capabilities disappear</li><li>Only server‑hosted JSON files and client JSON files remain available</li></ul><p>This demonstrates how environment variables can instantly switch OpenRose into <strong>server data file mode</strong>.</p><h3>Disabling Server‑Hosted JSON Files Using Environment Variables</h3><p>Next, the administrator sets:</p><pre>OfflineContent__StorageFolder=&quot;&quot;</pre><p>This disables the server‑hosted JSON folder — even though the JSON files still exist on disk.</p><p>After restarting:</p><ul><li>API connectivity is disabled</li><li>Server‑hosted JSON files are disabled</li><li>Only client JSON file mode remains</li></ul><p>This is the <strong>lightweight deployment mode</strong>, ideal for environments where users only need to open local JSON files.</p><h3>Why Empty‑Value Normalization Matters</h3><p>Different hosting environments treat empty strings differently.<br>For example:</p><ul><li>&quot;&quot;</li><li>&#39;&#39;</li><li>null</li><li>Whitespace</li></ul><p>OpenRose now includes a <strong>normalization layer</strong> that interprets all of these as “empty” or “not configured.”</p><p>This prevents misconfiguration across:</p><ul><li>Windows</li><li>Linux</li><li>Docker</li><li>Kubernetes</li><li>Cloud platforms</li></ul><p>Administrators can reliably disable features without worrying about how the underlying OS interprets empty values.</p><h3>Benefits for Enterprise Administrators</h3><p>AppSettings Overrides provide:</p><ul><li><strong>Security</strong><br>No need for file system access. Sensitive values stay out of source files.</li><li><strong>Operational Efficiency</strong><br>Switch modes instantly using environment variables.</li><li><strong>Automation‑Friendly Deployment</strong><br>Perfect for CI/CD pipelines and container orchestration.</li><li><strong>Consistency Across Environments</strong><br>Maintain a single read‑only “gold image” of OpenRose.</li><li><strong>Predictable Behavior</strong><br>Normalization ensures consistent interpretation of empty values.</li></ul><h3>Summary of What Administrators Can Override</h3><p>Using environment variables or command‑line parameters, you can override:</p><ul><li>API connectivity</li><li>Server‑hosted JSON folder</li><li>User file storage folder</li><li>Any other setting defined in <em>appsettings.json</em></li></ul><p>This gives you full control over how OpenRose behaves in each environment.</p><h3>The Advantages of Using an Open‑Source Requirements Management Tool</h3><p>Modern projects — whether software, engineering, infrastructure, or business transformation — depend heavily on clear, traceable, and well‑structured requirements. A dedicated requirements management tool helps teams avoid ambiguity, reduce rework, and maintain alignment across stakeholders. OpenRose strengthens this foundation by offering a structured environment where requirements, dependencies, and project artifacts are organized consistently. Unlike ad‑hoc documents or spreadsheets, OpenRose ensures that every requirement is captured, versioned, and traceable, giving teams confidence that they are always working with accurate and up‑to‑date information.</p><p>One of the most compelling advantages of OpenRose is its <strong>open‑source commitment</strong>. Many requirements tools are locked behind expensive licenses, proprietary formats, or restrictive deployment models. OpenRose takes the opposite approach: it is free, transparent, and community‑driven. This means administrators and teams can deploy it anywhere — on‑premises, in the cloud, or in isolated environments — without worrying about vendor lock‑in or unexpected costs. The open‑source model also ensures long‑term sustainability; even if organizational needs evolve, teams retain full control over their data, deployment strategy, and integration workflows.</p><p>Community involvement is another major strength. OpenRose evolves through real‑world feedback from practitioners, analysts, engineers, and administrators who use it daily. This creates a development cycle that is practical, responsive, and grounded in real project challenges — not theoretical features. When users request improvements, report issues, or contribute enhancements, those changes benefit the entire ecosystem. This collaborative model accelerates innovation and ensures that OpenRose remains aligned with modern requirements management practices.</p><p>Finally, OpenRose’s transparency fosters trust. Every feature, configuration option, and architectural decision is visible to the community. Administrators can audit the codebase, understand how data flows through the system, and verify that security practices meet their organizational standards. This level of openness is rare in commercial tools and is especially valuable for teams working in regulated industries or sensitive environments. Combined with flexible deployment modes and robust configuration options like AppSettings Overrides, OpenRose offers a powerful, secure, and adaptable platform for managing requirements at scale.</p><h3>Contributing to OpenRose</h3><p>OpenRose is a community‑driven project.<br>Administrators and developers can:</p><ul><li>Share feedback</li><li>Suggest improvements</li><li>Report issues</li><li>Submit pull requests</li></ul><p>You can contribute directly through the GitHub repository or send comments via email.</p><p>If you want to explore the broader ecosystem, you can learn more about <strong>requirements management platforms</strong>.</p><h3>Final Thoughts</h3><p>AppSettings Overrides represent a major leap forward for OpenRose.<br>They make deployments:</p><ul><li>Safer</li><li>More flexible</li><li>Easier to automate</li><li>Better suited for modern enterprise environments</li></ul><p>Whether you’re hosting OpenRose for a team or deploying it in a cloud environment, these capabilities give you precise control over how the application behaves — without ever touching <em>appsettings.json</em>.</p><blockquote>OpenRose, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Arh1wvmx9STkhvAB2GCsOw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6870386af1d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhanced Logging : A Deeper Look at Server‑Hosted JSON Data, User File Storage, and…]]></title>
            <link>https://medium.com/@openrose/enhanced-logging-a-deeper-look-at-server-hosted-json-data-user-file-storage-and-742c7ed0ab30?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/742c7ed0ab30</guid>
            <category><![CDATA[blazor]]></category>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 18:02:53 GMT</pubDate>
            <atom:updated>2026-08-26T18:02:53.368Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhanced Logging : A Deeper Look at Server‑Hosted JSON Data, User File Storage, and Environment‑Driven Configuration</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2NT9CXG4am8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2NT9CXG4am8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2NT9CXG4am8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dae73adc8b3900358ab4a5a34adbd0d2/href">https://medium.com/media/dae73adc8b3900358ab4a5a34adbd0d2/href</a></iframe><p>OpenRose continues to evolve as a community‑driven, open‑source <strong>requirements management tool</strong> built on .NET and Blazor. One of the most important improvements introduced recently is <strong>enhanced startup logging</strong> — a feature designed to help administrators, DevOps engineers, and self‑hosters understand exactly how their OpenRose deployment is configured at runtime.</p><p>This blog post transforms your raw transcript into a structured, SEO‑friendly article that explains the new logging capabilities, why they matter, and how teams can use them to manage server‑hosted JSON data and static user files more effectively.</p><h3>What Enhanced Logging Brings to OpenRose</h3><p><strong>Takeaway:</strong> OpenRose now provides clear, structured startup logs that reveal how the application resolves configuration values, including server‑hosted JSON data folders, user file storage paths, and environment‑variable overrides.</p><p>These logs are especially valuable for:</p><ul><li>Administrators deploying OpenRose on shared servers</li><li>DevOps teams automating deployments</li><li>Users hosting read‑only JSON data views</li><li>Anyone relying on static media files referenced inside requirements</li></ul><p>The improved logging ensures that every OpenRose instance starts with complete transparency about where data is stored, how it is accessed, and which configuration source (appsettings.json or environment variables) is in effect.</p><h3>Understanding Server‑Hosted JSON Data Files</h3><p>OpenRose supports multiple startup modes, including a <strong>server‑hosted data file view</strong>. In this mode, users can export project data as JSON and place it in a server folder for read‑only access.</p><h3>How OpenRose Logs Offline JSON Data</h3><p>At startup, the Web UI logs:</p><ul><li>The <strong>connection mode</strong> (e.g., connected to API at localhost:6736)</li><li>The <strong>offline JSON data folder</strong></li><li>Whether the folder path came from <strong>appsettings.json</strong> or an <strong>environment variable</strong></li><li>A list of all JSON files detected at startup</li></ul><p>This means administrators can immediately see:</p><ul><li>Which folder OpenRose is scanning</li><li>Whether the configuration was overridden</li><li>Which projects are currently hosted</li></ul><p>For example, the log might show:</p><ul><li>Offline content folder: C:\OpenRoseData\OfflineFiles</li><li>Source: Environment variable</li><li>Detected files: HS2.json, ScotlandTrip.json, StockTradingPlatform.json</li></ul><p>These files appear directly in the <strong>Server Data Files</strong> view inside the Web UI.</p><h3>Why Environment Variables Matter</h3><p>OpenRose supports configuration through both <strong>appsettings.json</strong> and <strong>environment variables</strong>. The enhanced logging makes it clear which source is being used.</p><h3>Benefits of Environment‑Variable Overrides</h3><ul><li>No need to modify appsettings.json during upgrades</li><li>Cleaner deployment pipelines</li><li>Easier containerization (Docker, Kubernetes, etc.)</li><li>Consistent configuration across environments</li></ul><p>The logs explicitly state when an environment variable overrides a setting, helping administrators avoid confusion and misconfiguration.</p><p>If you want to explore this topic further, you can dive deeper into <strong>environment‑based configuration</strong>.</p><h3>User File Storage: Hosting Static Media Files</h3><p>Many OpenRose projects reference images or other static files — maps, diagrams, architecture sketches, or photos. These files can be stored in a <strong>user file storage folder</strong> on the server.</p><h3>What the Logs Reveal</h3><p>At startup, OpenRose logs:</p><ul><li>Whether user file storage is enabled</li><li>The default folder from appsettings.json</li><li>The actual folder used (if overridden)</li><li>The resolved root path for static media</li></ul><p>For example:</p><ul><li>Default: ./UserFiles</li><li>Actual: C:\OpenData\UserFiles</li><li>Source: Environment variable</li></ul><p>This helps administrators confirm that media files are accessible and correctly mapped.</p><h3>How Media Files Are Referenced</h3><p>OpenRose exposes static files through:</p><ul><li>/userfiles/...</li><li>/media/...</li></ul><p>If a project references media/EverestHimalaya.jpg, OpenRose resolves it using the configured root folder.</p><p>This allows images to appear in:</p><ul><li>Live connected mode</li><li>Read‑only server‑hosted JSON views</li><li>Any client accessing the deployment</li></ul><p>You can explore how OpenRose handles media by looking at <strong>static file hosting</strong>.</p><h3>Demonstrating the Workflow: Exporting and Hosting a Project</h3><p>The transcript describes a practical example using the <strong>Mountain Trekking</strong> project:</p><ol><li>Export the project from OpenRose</li><li>Copy the JSON file into the offline folder</li><li>Refresh the server‑hosted data view</li><li>See the project appear immediately</li><li>Confirm that referenced images load correctly from the user file storage folder</li></ol><p>The logs show:</p><ul><li>The new JSON file detected</li><li>The static image path resolved</li><li>The image accessible via localhost:7673/media/...</li></ul><p>This demonstrates how seamlessly OpenRose integrates JSON data hosting with static media serving.</p><h3>Why Enhanced Logging Matters for Administrators</h3><p>The new logging system provides:</p><ul><li>Clear visibility into configuration sources</li><li>Immediate feedback on folder paths</li><li>Automatic listing of hosted JSON files</li><li>Confirmation of static file root paths</li><li>Insight into how OpenRose resolves environment variables</li></ul><p>This is essential for:</p><ul><li>Troubleshooting</li><li>Deployment automation</li><li>Multi‑environment setups</li><li>Server migrations</li><li>Version upgrades</li></ul><p>Administrators can now understand the entire configuration landscape without digging through multiple files.</p><h3>Best Practices for OpenRose Deployment</h3><p>To ensure smooth upgrades and predictable behavior:</p><h3>Recommended Approach</h3><p>Use <strong>environment variables</strong> for:</p><ul><li>Offline JSON data folder</li><li>User file storage folder</li><li>API base URL</li><li>Port configuration</li></ul><p>This avoids the need to modify appsettings.json during version updates.</p><p>If you want guidance on deployment strategy, explore <strong>OpenRose deployment best practices</strong>.</p><h3>Advanced .NET and Blazor Techniques Behind OpenRose Startup Modes and Logging</h3><p>The enhanced logging capabilities in OpenRose are not just operational conveniences — they demonstrate several advanced techniques available in <strong>.NET</strong>, <strong>.NET Core</strong>, and <strong>Blazor</strong>. These techniques allow OpenRose to support flexible startup modes, dynamic configuration, and transparent reporting of server‑hosted JSON paths and user file storage locations.</p><h3>Startup Modes Powered by Modern .NET Configuration</h3><p>OpenRose uses the .NET Core configuration pipeline to support multiple startup modes, including:</p><ul><li>Connected API mode</li><li>Server‑hosted JSON read‑only mode</li><li>Hybrid modes combining API and offline data</li></ul><p>This is achieved through layered configuration providers such as:</p><ul><li>Environment variables</li><li>appsettings.json</li><li>Command‑line arguments</li><li>In‑memory configuration sources</li></ul><p>The enhanced logging feature shows developers exactly <strong>which configuration source was used</strong>, making it easier to understand how .NET resolves values at runtime.</p><p>Developers who want to adopt similar patterns can explore <strong>configuration providers</strong> and <strong>environment‑variable overrides</strong> in their own applications.</p><h3>Logging Server JSON Paths and User File Storage</h3><p>OpenRose logs detailed information about:</p><ul><li>The resolved offline JSON folder</li><li>The resolved user file storage folder</li><li>Whether the values came from appsettings.json or environment variables</li><li>The list of JSON files detected at startup</li><li>The root path used for static media files</li></ul><p>This is implemented using:</p><ul><li>.NET’s built‑in logging abstractions</li><li>File provider APIs</li><li>Dependency‑injected storage services</li><li>Blazor components that surface the logged information to the UI</li></ul><p>These patterns demonstrate how developers can build applications that are both <strong>transparent</strong> and <strong>environment‑aware</strong>, especially when hosting static content or read‑only data files.</p><h3>Blazor Techniques for Dynamic Views</h3><p>The Web UI uses Blazor to dynamically present:</p><ul><li>Server‑hosted JSON project lists</li><li>Media previews resolved from static file paths</li><li>Connected vs read‑only views based on startup mode</li></ul><p>This is achieved through:</p><ul><li>Component‑driven architecture</li><li>Cascading parameters for application state</li><li>Routing that adapts to connected or offline modes</li><li>JS interop for certain UI behaviours</li></ul><p>Developers can learn from these patterns to build responsive, configuration‑aware Blazor applications.</p><h3>Why Developers Should Explore and Contribute</h3><p>The techniques used in OpenRose are intentionally designed to be accessible and educational for .NET and Blazor developers. By studying the enhanced logging and startup mode implementation, developers can learn how to:</p><ul><li>Build flexible configuration pipelines</li><li>Implement environment‑driven deployments</li><li>Host static content alongside JSON data</li><li>Create Blazor components that adapt to runtime configuration</li></ul><p>We encourage developers to:</p><ul><li>Review the source code</li><li>Experiment with the startup modes</li><li>Apply these patterns in their own projects</li><li>Share feedback or suggestions</li><li>Submit pull requests to help improve OpenRose</li></ul><p>The OpenRose GitHub repository is open to contributions from the community, and developers can send comments, ideas, or enhancements directly through issues or pull requests.</p><h3>Conclusion</h3><p>Enhanced logging in OpenRose is more than a technical improvement — it’s a major usability upgrade for administrators and DevOps teams. By clearly showing configuration sources, folder paths, and hosted content, OpenRose makes deployments more predictable, maintainable, and transparent.</p><p>This feature strengthens OpenRose’s position as a powerful, community‑driven <strong>requirements management platform</strong> that is free, open source, and built for real‑world project teams.</p><blockquote>OpenRose, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FtE9wm5iczagO0_cCClMgw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=742c7ed0ab30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Mobile‑Friendly Leap Forward: OpenRose Introduces Card‑Based Server Data File Views]]></title>
            <link>https://medium.com/@openrose/a-mobile-friendly-leap-forward-openrose-introduces-card-based-server-data-file-views-167ddbb04b0b?source=rss-a745b037e96b------2</link>
            <guid isPermaLink="false">https://medium.com/p/167ddbb04b0b</guid>
            <category><![CDATA[requirements-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[OpenRose]]></dc:creator>
            <pubDate>Sat, 22 Aug 2026 12:39:43 GMT</pubDate>
            <atom:updated>2026-08-22T12:39:43.314Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpFLfj5cHuJI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpFLfj5cHuJI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpFLfj5cHuJI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ce51eaac42ce54c1ce765dd1d3caf92/href">https://medium.com/media/9ce51eaac42ce54c1ce765dd1d3caf92/href</a></iframe><p>Modern requirements management demands clarity, accessibility, and speed — not just for analysts and engineers, but for every stakeholder who interacts with project data. Whether you’re a business analyst, a project manager, a product owner, or a sponsor reviewing progress, you need a tool that works seamlessly across devices and presents information in a clean, intuitive way.</p><p>OpenRose — the <strong>community‑driven, FREE, open‑source requirements management tool</strong> — continues to evolve with this mission in mind. Today, we’re excited to introduce a major usability improvement: <strong>a redesigned server‑side data file view</strong>, now presented as <strong>touch‑friendly cards</strong> instead of a traditional dropdown list.</p><p>This enhancement makes OpenRose dramatically more accessible on mobile devices, tablets, and touchscreen laptops, while also improving usability for desktop users who prefer quick, visual navigation.</p><h3>Why This Matters: Requirements Management Needs Better Accessibility</h3><p>Requirements management is no longer confined to desktop environments. Teams collaborate across continents, stakeholders review requirements on the go, and sponsors often access project data from tablets during steering committee meetings. A dropdown list — especially one containing dozens of exported project files — is cumbersome, slow, and unfriendly on touch devices.</p><p>This is a common challenge in requirements engineering. When teams export data for offline review, they often lose:</p><ul><li>Traceability</li><li>Visual hierarchy</li><li>Attached images</li><li>Diagrams</li><li>Metadata</li><li>Cost and estimation details</li></ul><p>Static documents like PDFs or Word files struggle to preserve the richness of requirements data. They flatten structure, break links, and remove interactivity — all of which are essential for <strong>requirements engineering</strong>, <strong>stakeholder communication</strong>, and <strong>project governance</strong>.</p><p>OpenRose solves this by allowing teams to <strong>host JSON‑based project snapshots directly on the server</strong>, providing a <strong>read‑only, interactive, visually rich view</strong> that mirrors the full application experience.</p><h3>Introducing Card‑Based Server Data File Views</h3><p>The new UI replaces the old dropdown list with a <strong>clean grid of cards</strong>, each representing a hosted project file. This design is intentionally simple, visual, and touch‑friendly.</p><h3>Why Cards Are Better Than Dropdowns</h3><p>Cards offer several advantages:</p><ul><li><strong>Touchscreen‑friendly</strong>: Easy to tap, swipe, and scroll</li><li><strong>Visual clarity</strong>: Each file is presented as a distinct object</li><li><strong>Faster navigation</strong>: No need to open a dropdown and scroll through long lists</li><li><strong>Better for mobile users</strong>: Dropdowns are notoriously difficult on small screens</li><li><strong>Improved accessibility</strong>: Cards are easier to interact with for users with motor or visual challenges</li></ul><p>This aligns with modern UX principles in requirements management tools, where <strong>accessibility and speed</strong> directly impact productivity.</p><h3>A Read‑Only, Reliable Window Into Your Project Data</h3><p>One of the biggest strengths of OpenRose’s server‑hosted data files is that they are <strong>read‑only</strong>. This ensures:</p><ul><li>No accidental edits</li><li>No risk of corrupting project data</li><li>Safe sharing with external partners</li><li>Consistent reference points for stakeholders</li></ul><p>This is crucial for <strong>project sponsors</strong>, <strong>business owners</strong>, and <strong>external reviewers</strong> who need visibility but should not modify requirements.</p><h3>Why JSON‑Hosted Views Beat Traditional Document Exports</h3><p>Many requirements tools attempt to export data into PDFs or Word documents. But this approach is fundamentally flawed:</p><p>JSON‑hosted views solve this by preserving:</p><ul><li>Hierarchy</li><li>Traceability</li><li>Images</li><li>Diagrams</li><li>Metadata</li><li>Estimation values</li><li>Status, priority, severity</li></ul><p>This is a massive advantage for <strong>requirements engineering</strong>, where context and relationships matter as much as the requirement text itself.</p><p>Instead of flattening your project into a static document, OpenRose gives you a <strong>live, interactive snapshot</strong> that behaves like the connected mode — but without write access.</p><h3>Consistent Look and Feel Across Connected and Read‑Only Modes</h3><p>This consistency is vital for:</p><ul><li>Training new team members</li><li>Reducing cognitive load</li><li>Ensuring stakeholders don’t get confused by different interfaces</li><li>Maintaining trust in the data</li></ul><p>Whether you’re in connected mode or viewing a server‑hosted snapshot, the experience is identical — except that the hosted version is safely read‑only.</p><h3>Perfect for Mobile, Tablet, and Touchscreen Users</h3><p>OpenRose’s new card‑based UI shines on mobile devices. Requirements management is increasingly mobile, with stakeholders reviewing data:</p><ul><li>During travel</li><li>In meetings</li><li>On construction sites</li><li>In workshops</li><li>At client locations</li></ul><p>The new UI ensures that:</p><ul><li>Cards are easy to tap</li><li>Scrolling is smooth</li><li>Images and diagrams load beautifully</li><li>Traceability navigation works flawlessly</li><li>JSON views remain fully interactive</li></ul><p>This is a major leap forward for <strong>mobile‑first requirements management</strong>.</p><h3>Traceability, Images, Diagrams — All Preserved Perfectly</h3><p>This is a huge advantage over PDF exports, which often break:</p><ul><li>Traceability</li><li>Embedded images</li><li>Navigation</li><li>Hierarchical structure</li></ul><p>OpenRose keeps everything intact, making it ideal for:</p><ul><li>Business analysts</li><li>Systems engineers</li><li>Product owners</li><li>QA teams</li><li>Sponsors reviewing scope</li><li>External partners validating requirements</li></ul><h3>A Community‑Driven Feature Built With User Feedback</h3><p>This is one of OpenRose’s greatest strengths: it is <strong>community‑driven</strong>, <strong>open‑source</strong>, and <strong>free</strong>. Enhancements like the new card‑based UI come directly from real user feedback — especially from teams who rely on mobile devices.</p><p>This ensures OpenRose continues to evolve into a world‑class <strong>requirements management</strong> and <strong>business analysis</strong> tool.</p><h3>Conclusion: A Small Change With a Big Impact</h3><p>The new card‑based server data file view may seem like a small UI enhancement, but it dramatically improves:</p><ul><li>Mobile usability</li><li>Touchscreen navigation</li><li>Stakeholder accessibility</li><li>Read‑only data sharing</li><li>Requirements review workflows</li><li>Consistency across devices</li></ul><p>OpenRose continues to prove that powerful requirements management doesn’t need to be expensive. It can be <strong>free</strong>, <strong>open‑source</strong>, <strong>community‑driven</strong>, and still deliver enterprise‑grade capabilities.</p><blockquote>OpenRose, a free and open-source requirements management application / tool. For more information, visit</blockquote><blockquote><a href="https://github.com/openrose">https://github.com/openrose</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHIJJdZMX5sI2Mp1JKPMaA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=167ddbb04b0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>