Hi, thanks for this idea! We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

Hi @GQ Sparks! Abby here from Lucid. I think you, and others who might come across this topic in the future, might be interested in Lucid’s Agile Trusted User Group. This group is made up of passionate, experienced users who regularly use agile methodologies in their work. As part of this group, you’ll have the opportunity to connect directly with Lucid’s product team and share insights about your workflows, pain points, and needs, shaping the future of Lucid’s agile tools. 🎉 You can learn more and apply here. Thanks!

My team and organization would benefit greatly from this feature. I regularly import work items from Azure into Lucid, and use smart tables to analyze their state. This works great when analyzing all the items for a single parent Feature, select iterations, whose name matches the pattern, etc. However, since our organization uses Tags in Azure to group initiatives that span multiple features / iterations / naming conventions, I have to jump through hoops in Lucid to import all the work items that would otherwise be associated with a single Tag on the work item

this would defintely make life easier for pulling in multiple items that aren’t all under the same feature.

Thank you ​@brenthompson2 and ​@Astrid_G for adding your feedback to this thread. I can certainly understand why this would be beneficial. 

Our product teams are regularly reviewing feedback within this space as they continue to research new features and product enhancements. Your upvotes and comments to this post are the perfect ways to indicate your desire for this to be implemented. 

Adding this TAG filter could also go hand in hand with adding an Assignee filter: 

I second this feature request

bump

Thank you ​@brad_renshaw, ​@sam.venter, and ​@brenthompson2 for taking the time to upvote this post and show your support for this feature!