Skip to main content
NathanRo1
Level 2
February 10, 2020
質問

Can I create a filter with a cross object reference to a custom field using $$USER?

  • February 10, 2020
  • 2 の返信
  • 558 ビュー
I'm trying to create an issue-based report filter that will match a user's region (using a custom user field called "IIT Region") to the project's region, using that same field applied to the project. Is it possible to use a user-based variable ($$USER) in such a cross object reference with a custom field? These attempts don't seem to be working: DE:$$USER:IIT Region=DE:project:IIT Region DE:$$USER:IIT Region_Mod=in or DE:$$USER:ID:IIT Region=DE:project:IIT Region DE:$$USER:ID:IIT Region_Mod=in Thanks in advance! Nathan Roberts
このトピックへの返信は締め切られました。

2 の返信

Doug_Den_Hoed_AtAppStore
Community Advisor
Doug_Den_Hoed_AtAppStoreCommunity Advisor
Community Advisor
February 11, 2020
Alas, no, Nathan, As per this super worth-bookmarking (or short-cutting, or tattooing on your forehead so you can read it in your selfies; however you keep track...) article explains, there are a limited number of built-in aspects of $$USER exposed. Instead, I invite you to consider creating a Filter and/or providing Prompts (regular, or Custom) on your Issue report. I would not recommend copying every report for the sake of changing (only) the filter, since over time, it's likely you'll need to adjust other aspects of the report, and then curse the effort to chase it through every such copy. Regards, Doug Doug Den Hoed - AtAppStore
Learn more at www.atappstore.com, email doug.denhoed@atappstore.com, or tag me here @Doug_Den_Hoed_AtAppStore.
NathanRo1作成者
Level 2
February 11, 2020
Thank you Doug! I really appreciate your quick answer. I actually read through that article during my research but I didn't see anything directly on point. Regardless, I trust that you know what you're talking about and I see what you mean about it being a discrete number of options. I will try to find some other way to accomplish my goal. Thanks again! Nathan Nathan Roberts
契約条件Accessibility statement

Loading footer...