Element Filtering in RTF generation not working 10

[Crush]

I'm having an issue when trying to generate an RTF document that filters for the status of requirements in pending or proposed.

If I set the element filter to pick up only pending items, it will find all the pending requirements within some packages but not others.

Is there something at the package level that could interfere with the RTF filter working properly?  

I really need to be able to filter for requirements within packages by their status.

Any help is greatly appreciated!

Thanks in advance.

 8-)

[alesliehughes]

The only filters that applied to packages are found on the options tab.

Step I used for a basic report.
On the Element Filters tab of the RTF Genarate dialog.
Add a filter Element.Satus
Changed condition to "One Of" and select from the list of Statuses.
Ensure the "Required" option is checked.
Generate your report.

Alistair

[Crush]

Thanks for the tip Aselie, however it doesnt seem to work that way either.

I added a filter under element filters in the RTF Generate dialog, and mde it condition "One Of" and selected the status (required was checked on both the element on the right and at the bottom left under Element Features).  
 
I have noticed one peculiar thing however.  IF the top level requirement has the same status as the one Im filtering for, THEN it will find any matching statuses in the sub requirements underneath that one.

For example.

1. Requirement A   <- Set Status to "Pending"
   1.1 Requirement A1
   1.2 Resuirement A2   (Status = pending)
   1.3 Requirement A3
   1.4 Requirement A4


When I set Requirement A to "pending" (even though it really isn't pending), and THEN run the report it will "See" Requirement A2 and put it into the report.

IF Requirement A is not set to pending it will never "see" Requirement A2 as pending and will NOT put it into the report.

Weird , huh?

 

[alesliehughes]

No, not weird.

The currently bahaviour of the engine is to only process child elements if the parent has been included.

Alistair

[Crush]

Ah.. so it WILL process it if the parent requirement is a match   , and it will NOT process it if the parent requirement is NOT a match?

I see, is there a plan to fix this in a future release?

Thanks again.

[alesliehughes]

Yes, this is something we are planning for a future release.

Alistair