Implementation - Copy Requirements Data

 


Copy feature supports copying of Project, ItemzType or Itemz with it's sub Itemz hierarchy structure. In this article we will learn about this new feature introduced in OpenRose version 0.1.2-243. 

Direct Link to YouTube Video : 

https://www.youtube.com/watch?v=2bExGaaQSVc

Video Transcript :

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

https://github.com/openrose. 

In today’s blog post, we’re excited to introduce a new feature: Copy Data. This feature is designed to streamline your project management processes, especially for charity fundraising initiatives.

Understanding the Project Structure

Before diving into the copy functionality, let’s take a look at the project structure we’ll be using in this example. Within OpenRose, we have four projects, and today we’ll focus on the Charity Fundraising Project.

Project Stages

The Charity Fundraising Project is organized into three main stages:

  1. Pre-Fundraising Preparation
  2. Conducting the Fundraising Event
  3. Post-Fundraising Activities

Pre-Fundraising Preparation

In this stage, we define high-level requirements, which can be further broken down if necessary. Key activities include:

·         Defining goals for the fundraising campaign

·         Identifying the target audience

·         Planning the fundraising campaign

·         Securing necessary permissions and approvals

Conducting the Fundraising Event

This stage involves 

  • executing the fundraising event
  • engaging with participants and volunteers 
  • monitoring event progress 
  • collecting donations

Post-Fundraising Activities

After the event, we 

  • summarize campaign performance
  • thank donors and volunteers
  • distribute post-event reports
  • create social media content to showcase fundraising success. 

This includes planning video content, producing and editing video reels, and promoting them across various platforms.

The Copy Data Feature

Now, let’s explore how the new Copy Data feature works at different levels within the project.

1. Copying Individual Requirements

You can copy individual requirements, whether they are parent items or leaf nodes. For example, if you want to copy the "Video Editing" requirement, simply:

·         Copy the ID of the requirement.

·         Open the copy option and select "Copy an Item."

·         Paste the ID and confirm the copy.

The copied requirement will appear directly below the original, with a suffix indicating it’s a copy (e.g., “_copy” followed by a random number).

2. Copying Parent Items with Children

To copy a parent item that has children, follow the same process:

·         Copy the ID of the parent item.

·         Use the copy option to select "Copy an Item."

·         Paste the ID and confirm.

This will replicate the entire structure, including all child requirements, while maintaining the original data attributes.

3. Copying Entire Item Types

If you need to copy an entire item type, simply:

·         Copy the ID of the item type.

·         Use the copy option to select "Copy Item Type."

·         Confirm the action.

This will create a complete duplicate of the ItemzType, including all associated requirements.

4. Copying Entire Projects

To copy an entire project, you can:

·         Copy the project ID.

·         Use the copy option to select "Copy Project."

·         Confirm the action.

The copied project will retain all data and structure, making it easy to replicate successful fundraising strategies.

Maintaining Traceability

One of the standout features of OpenRose is its ability to maintain traceability. When you copy requirements, the relationships between Itemz are preserved. For instance, if you copy a requirement that has dependencies, those links will remain intact in the copied project.

Example of Traceability

If you copy the "Engage Participants and Volunteers" requirement, it will still reference the "Publish and Promote" requirement, ensuring that all necessary connections are maintained.

Conclusion

The new Copy Data feature in OpenRose is designed to enhance your project management experience, particularly for charity fundraising projects. By allowing you to copy data at various levels—individual requirements, parent items, item types, and entire projects—you can save time and streamline your processes.

We encourage you to explore this feature in the latest version of OpenRose (0.1.2-243) and share your feedback with us. Remember, OpenRose is free, open-source, and built for the community. Thank you for your time, and happy fundraising!

For more updates, don’t forget to follow us on our GitHub page and share your experiences with others.

 Have a great day!




Comments

Post a Comment

Popular posts from this blog

Introduction to OpenRose - Requirements Management

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

What is Requirement?

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

Details View - OpenRose - Requirements Management

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