It's all about the answers!

Ask a question

In RTC Product Backlog Plan, need to filter ONLY to show the Unassigned values for "Proposed" custom attribute


Meghana H (26111) | asked May 02, 4:37 a.m.
We have an RTC "Product Backlog" Plan where I need to filter ONLY to show the Unassigned values for "Proposed" attribute type in Feature and Epic work items. Proposed is an iteration type custom attribute in our SAFe template. I tried in all ways but somehow I am unable to get only the unassigned Epic and Feature types
I also tried as per the suggestion here, But still after adding multiple excludes for Proposed with the iteration I don't want to see as this works like an OR, it still doesn't work

It is also seen that we can filter ONLY the unassigned values for built in attributes like filed against and priority.

Please see the attachment below

2 answers



permanent link
Ralph Schoon (63.6k33646) | answered May 02, 5:19 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Your expression does not make sense to me. You would type Proposed: or proposed: and then select unassigned. The choice should be selectable from content assist. So the expression would look something like Proposed:unassigned.

In addition, we do not have filter, we have an exclude. So when you exclude the Proposed:unassigned, you would not see any of the ones you want to see. You would have to exclude all other proposed values to only see the ones you want to see.

I would expect this to work for custom enumerations, but I can't test that at the moment.


Comments
Meghana H commented May 02, 5:33 a.m.
Hi Ralph

We have also tried to exclude only to see the ones we wanted to by trying out expressions like below:
Proposed:%Unassigned%
Proposed:"Unassigned"
Proposed:Unassigned
But none of the above ones are working
Thank You

Meghana H commented May 04, 11:14 a.m.
We tried for sure both, with ! and without. 
!Proposed:Unassigned
Assuming it shall have any impact to the list shown in the image, but none of those combinations did show the respectively expected filter result.

permanent link
Ralph Schoon (63.6k33646) | answered May 06, 5:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I created a custom enumeration, added an attribute using it to a work item type, added the attribute to the plan attributes, created filters to filter out all values, except unassigned, and it works as expected. 7.0.3, Enumeration is stored in the process XML.  

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.