Move Itemz Type - Requirements Management

 


Move Itemz Type - Requirements Management

OpenRose - Requirements Management

An Open Source and FREE Requirements Management Application / Tool

Direct Link to YouTube Video : https://www.youtube.com/watch?v=3R8CX9Vj6HM

Video Transcript :

Hello, this is OpenRose, a free requirements management application. You can find it at https://github.com/openrose.

Today we are going to talk about moving item types. Let me go into the project list and open the first project. This is a sample project that I have created based on a document published by Barclays Bank regarding tariffs for personal customers. Here is the link to that document. I have tried converting part of that document into the structure in this project where we have around five item types.

Let me talk about the "About Our Tariff" item type. When I expand that, we can see requirements or items sitting under that item type. Looking at the first requirement, we can see it has the name, status, priority, severity, and description, which are the standard properties. Along with that, we have one traceability, which is a child trace to "Eligibility for Premier Banking." When I click on open, it is a requirement sitting at this location under a separate item type called "Account Eligibility and Fees." There is a link to this item, which is a parent link, again going back to the same original item we started looking at.

To show an example of moving this particular item type, including all child requirements, to a completely separate project, let me first go into the project list and create a new project. I'm going to call it "Dummy" with the status "New" and "D" as the description. The new project is now created along with the Parking Lot item type, which is a system item type. We only have one item type here. Let me refresh it one more time. It is just the Parking Lot.

Going back into the Barclays project, I will move the "About Our Tariff" item type and all its children by copying the ID of the "About Our Tariff" item type. Then, open the "Item Type Under" option, which is for moving item types under another. It opens up in a new tab because I did a control-click. I will pass in the source ID and select the target project. We do allow choosing one of the projects available in your repository. Let's say I'm going to move it to the Dummy project. I can decide if it should go at the bottom or top of the child item types list. We know there is one item type called "Parking Lot" already there. I will push "About Our Tariff" to the top location within that project, which means the Parking Lot will be the last one, and "About Our Tariff" will be the top one.

After completing the move, it is successfully completed. Let's refresh the Barclays project to verify that the item type is gone from this location. Jumping back to the Dummy project, we can see "About Our Tariff" has been moved to that location, and Parking Lot is at the bottom because we moved "About Our Tariff" to the top location.

Let's move it back to its original location. I will select that item type and then select the project "Barclays Tariff" and place it at the top location. It should be moved back to its original location.

The second option we have is to move an item type within the project. Let me close the screen and go back to the Barclays project. When I open this up in the Treeview, I see the item types. At the time of recording this demo, we didn't have the option to move item types up and down within the project at that level, which is level two as we see here. To do that, we have to go to the Details view. In the Details view, we have buttons to move item types up and down. Let me move "About Our Tariff" further down to the bottom below the Parking Lot. When I refresh my Treeview, we should see that "About Our Tariff" has gone to the bottom, even below the Parking Lot. You can move data up and down without any issue there.

The other thing I wanted to demonstrate was moving between specific item types. To do that, let me go to the Dummy project in the Details view. I will create a new item type. This will be "Item Type Test 1," and I will use the same for the description. The new item type is now created.

What I want to do is move an item type in between Parking Lot and Item Type Test 1. I will go back to our original project, Barclays, and show you that one of the items in "About Our Tariff" has a link. We saw that link already, which is "Eligibility for Premier Banking." This particular link is available at this location in Barclays. When we move the "About Our Tariff" item type, let's select that and move it in between. I will pass the source item ID, select the target item ID, and in the Dummy project, I will select Parking Lot as the first item. When we pass that information, it automatically selects the second item ID. It means we are trying to push "About Our Tariff" in between Parking Lot and Item Type Test 1. After moving it, refreshing the screen in the Dummy view shows it has been moved there.

Remember, we have a trace from this location, which is a requirement we had in the Barclays project. That trace is still there and should be kept as it is. We should be able to jump from the Dummy project to the Barclays project to see that particular trace information. Trace data is not lost when you move an item type from one project to another, and that link is still there. Be aware of that particular capability or feature.

We can move item types up and down within the project or across different projects. When moving across different projects, we decide if it goes at the top or bottom level using the "Item Type Under Move" option. If we are moving using the "Item Type Between" option, we have to decide which two item types to use as the target to move the source item type in between.

With that, I would like to conclude this video. Thanks a lot for your time. Have a great day!

Document Ref:

 

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