Grouper WS does not behave as expected with some attribute call request

I was hoping to be able to return a list of memberships for a user, but only if the group itself had a certain attribute (in this use case, we have one that marks that it's a "working group", so we can display to people in a separate UI that they are in said working groups). 

The way we do it now is to get a list of the person's groups, then we have to do a call to look at each group and see if it has that attribute on it. 

I was chatting with Chad about this in one call and trying to do something similar and we found a few things that he said we should capture in JIRA.

Here's what Chad said.

"There is likely a gap in what WS can do. I can get close, but don't get the results I expect
POST /grouper-ws/servicesRest/v1_6_000/subjects/GrouperSystem/memberships
{
  "WsRestGetMembershipsRequest":{
    "wsOwnerAttributeDefLookups": [
     

{         "name": "test:WSAttributeTest:comanagetemplate_actorDef"       }

    ]
  }
}
I don't know why it can search on an attributeDef and not an attributeName. But still it should return the group and it's not

{
  "WsRestFindGroupsRequest": {
    "wsQueryFilter":

{       "groupAttributeName": "test:WSAttributeTest:dumbMetadata",       "groupAttributeValue": "comanage",       "queryFilterType": "FIND_BY_EXACT_ATTRIBUTE"     }

  }
}

this should at least get the groups, but it (1) assumes its metadata on an assignment and not a direct value, and (2) for some reason prepends the attribute with "etc:legacy:attribute:legacyAttribute_", so your attribute would need to be in that folder"