| Excerpt | ||||
|---|---|---|---|---|
| ||||
Documentation on the estimates and external properties. Discover what they are and how to use them now. |
| Info |
|---|
Requirement Yogi 3.6 and aboveThere have been some updates and the tab shown in the video and screenshot is no longer called Estimates, but External PropertiessProperties. You can now edit External properties in the Traceability Matrix. |
| Info |
|---|
Requirement Yogi 3.0 and aboveExternal properties can be used for estimates, testing, and to track any other data about the requirement. |
You want a quick and easy way to learn about External Properties, check out our video tutorial: https://www.youtube.com/watch?v=c_UAD72UmEc
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
As opposed to inline properties, external properties are not visible in the original page. You can edit them without disturbing the author of the requirements,
They are displayed in the requirement popup, identified with a little asterisk (*),
Find all existing External properties of your space, in the "External Properties" tab,
They can be modified by anyone with edit permissions on the space,
Click on an external property and you will be sent to the traceability matrix, where you will be able to click on the toggle to edit them.
External properties are simply a way to track data about requirements without disturbing the viewers of the original page: Group your requirements by adding a tag, assign a cost, list the impacted components, or add subjective information about them. Beware though: They are visible by everyone in the space, in the popup of the requirement.
Estimates
This is our main usecase use case for the external properties. You can use them to perform an estimation of your project:
ℹ️ You can define operations such as sum, min, max, average and count, and they are updated when you fill in the values.
ℹ️ Notice that this looks very much like the traceability matrix, and we even have the little menus which allow you to create columns: The two matrices are using the same back-end, we just add editable fields for the estimates.
Hijack the estimates to build your own testing solution
Although our primary example of external properties is for estimates, you can extend them with various types.
Here is an example using external properties (checkbox and comments) to tick requirements which have been tested:
ℹ️ Notice how the left handside of the matrix is the traceability matrix: You can retrieve as many columns as desired, to bring up the context that is necessary to fulfill your task.
Administering the external properties
External properties are global to the instance, and are administered in the Requirement Yogi administration.
You can change the data type,
You can click on the property to search for them (It will reuse the last space),
You can delete unused ones.
