Easy way to change requirement status?

[ps_ea]

Hi all,

in order to change the status, I have to select each requirement element, open the properties, and choose a new status from the drop down list.

Is there an easier, faster way to do this? A way to get this into the context menu, or a keyboard shortcut? And a possibility to change multiple elements together?

Thanks! Peter

[skiwi]

Use View on the menu toolbar to open the Element properties pane.
Selecting the element then displays the property and you can change it.

Bug alert: selecting several elements and changing a property does not, as you would expect, change the property on all selected elements. (EAUI)

[philchudley]

There is a sort of way round the inability to select elements and then apply a change to the selection.

1) Create a temporary package in the project browser, say called Change Status
2) Select the Requirement Elements that you would like to change the status of and move them (temporarily) into the package created in 1)
3) Right click the package and select Package Control | Update Package Status...
4) Complete the dialog so as to update the status properties of all elements in this package
5) Move the Requirement Elements back to their original position in the Project Browser

A bit clunky but it works, the only other alternative I know is to write a script

Cheers

Phil

[Zaid]

Use View on the menu toolbar to open the Element properties pane.
Selecting the element then displays the property and you can change it.

Bug alert: selecting several elements and changing a property does not, as you would expect, change the property on all selected elements. (EAUI)

Thanks for the suggestion - it really saves time!

[wolfgang.uhr]

There is a sort of way round the inability to select elements and then apply a change to the selection. ...

In my version of EA (8.0.63) it does not work. The last step changes the properties of the package itself but not the properties of the elements inside the package.

[Peter Doomen]

Instead of working with requirement statuses as a property of the element, which is the most common way and also how I do it, you could work with activity regions: one region per status.

When you then drag a requirement to a different region, it becomes a child of the status in the model tree. That way, you can even report on requirements more easily (e.g. they'll be grouped by status in reports).