How do I filter on REQs to show REQs with no requested items in the related list at the bottom?

[chrisperry]

I am trying to run a filter on the task table for 'My Groups Work' to show any incidents, CATTSKs, changes, etc. that a group needs to actually take action on / fulfill.   Part of the requirement is to show REQs which have not yet been transferred to an incident (easy enough, Transferred to = empty), or that have no requested items associated with them (that is the tricky part).

I can't figure out how to remove the REQs that DO have an RITM associated with them in the related list... it is kind of tricky since the RITMs are shown as a related list at the bottom of the REQ and therefore we cannot access info about those tickets from the REQ itself.

In Fuji, we had a solution where the filter was the REQ's price = empty, because the REQ's price was set to $0.00 whenever an RITM was actually added to the REQ.   However, this filter was broken when we upgraded to Helsinki, as it appears that Helsinki now lists all empty REQ prices = $0.00, regardless of whether an RITM has been added or not.

Any help would be much appreciated, thanks!

[chrisperry]

Thanks Chuck, logically speaking - that makes sense.   I would like to find a way to achieve this functionality without adding new customizations/configuration, so I am going to keep investigating but this solution will work if I am still unable to find anything.   Thanks

[Chuck Tomasi]

You can do it from a script, but there is no list filter capability that says "Show me only the REQ records with no child RITMs."

[chrisperry]

Right... I was kind of thinking that myself actually.   With that in mind, any ideas on what that javascript statement would look like in the filter to say 'REQ w/ no RITMs added'?

[Chuck Tomasi]

Hi Christopher,

I don't know if we're on the same page with this... in order to write a javascript statement in the filter, you need to be able to compare it against an existing field (e.g. start date < javascript:gs.daysAgo(5)) implies there is a start_date field. While I could create the javascript part for you (basically putting the above code in a function in a script include), there's nothing to compare that against. Hence the problem. You cannot do this on a list filter. Sorry for the confusion.

[chrisperry]

understood, thanks Chuck.   Yeah I was having a tough time conceptualizing this one as well, it wouldn't be possible to do something along the lines of an iterative script include which looks for REQ# != CATTSK.RITM.REQ?   In other words if the REQ# exists as a CATTSK's RITM's REQ, then do not display.