The Ultimate Guide To Harnessing The Power Of Project Lexicon Saved Boards

What Saved Boards Actually Do in Project Lexicon

Most people treat saved boards like a fancy bookmark system. That's not what they're for. A saved board in Project Lexicon is a persistent query result that re-evaluates every time it opens. You set up filters, tags, assignees, date ranges, whatever combinations you need, and it remembers them. When you come back tomorrow, next week, or next month, the board loads with exactly the items matching those conditions. No re-filtering. No manual searching. Just the data you told it to show. I spent three weeks trying to get our team to use them properly because everyone kept saving boards with "due this week" and then wondering why they were always empty on Fridays. The problem wasn't the feature. It was that people don't think about what filters to lock in. A saved board with a dynamic date range like "in progress AND updated within last 14 days" does something completely different than one hardcoded to a specific sprint. The first one ages gracefully. The second one becomes useless the moment the sprint ends.

The Ultimate Guide To Harnessing The Power Of Project Lexicon Saved Boards

Step one: stop creating saved boards for one-off views.

If you only need to see something once, save the filter manually inside the current session and move on. Saved boards are expensive in terms of mental overhead to maintain. Every board you create is one more thing someone will open six months later and wonder why it still exists. Use them for patterns that repeat. Weekly status reviews. Bug triage pipelines. Onboarding checklists for new hires. Anything that returns on a schedule or follows a consistent logic.

Step two: build your filters in layers.

Start with the broadest constraint that matters. Usually that's a tag or a project assignment. Then narrow by status. Then by assignee or date. Don't reverse that order. I watched a junior PM save a board filtering by "assigned to me" first, then "status equals blocked," and then spend twenty minutes trying to figure out why the board showed zero items when he switched contexts between projects. The fix was flipping the hierarchy so the project scope locked in before anything else. It takes longer to set up but it works when you actually need it.

Step three: name them like you're filing documents.

"Board 1" or "My Stuff" gets you nowhere. Use a naming convention that tells you what it does without opening it. Something like "QA - Active Bugs - High Priority" or "Design Review - Waiting on Feedback." If you can't describe what the board shows in six words or fewer, you probably don't need it saved yet.

The Edge Case Nobody Warns You About

Here's a problem I ran into that took me entirely too long to diagnose. I had a saved board filtering by custom field value "Client: Acme Corp" and it worked perfectly for eight months. Then Acme Corp got acquired and the client tag was changed to "Acme Holdings" across fifty-plus records. The saved board didn't break. It silently returned zero results. No error message. No warning. Just an empty board. I spent two days thinking I'd broken the filter syntax before I realized the underlying data had moved and my query was still pointing at the old value. The workaround: never rely on a single custom field value as your primary filter if that value is likely to change over time. Instead, build the board around a property that's more stable, like a project root or a category tag that maps to the org structure rather than a name. Then layer the client-specific field as a secondary filter so it excludes rather than defines the scope. That way when the name changes, the board still surfaces the relevant items, just tagged differently.

Advanced Filtering Tricks Most People Miss

Negation filters.

Project Lexicon supports "does not contain" and "is not equal to" in saved board queries. This is useful for things like excluding archived items from a board that otherwise pulls from an entire project, or filtering out completed tasks from a weekly review so you only see active work. Most people don't know this exists because it's buried under the advanced filter menu. Look for the small arrow next to each filter row. Click it and you get the full operator list.

Union queries.

You can save a board that combines two separate filter sets using OR logic. This is how you build a board that shows both "overdue tasks" and "tasks due today" in one view without manually combining them each time. The trick is setting the join mode correctly. If you set it to AND, you'll get items that are somehow both overdue and due today, which is impossible, so the board stays empty. Make sure you switch it to OR before saving.

Date math.

Saved boards support relative date expressions. "Due within next 7 days" works. "Created after last Monday" works. "Updated in the last 30 days" works. But "created in the current quarter" does not work unless you're on the enterprise tier. I learned that the hard way when a board I'd spent an hour configuring just showed everything instead of filtering by quarter. Checked the docs after and found that advanced date ranges require a higher subscription level. Not ideal, but worth knowing upfront.

Downsides and When to Avoid Saved Boards

Saved boards consume server resources on every load. In large projects with hundreds of members, having fifty active saved boards means fifty queries running simultaneously whenever people open their dashboards. The performance hit is usually small but noticeable if your instance already feels slow. If you're running a big org, audit your saved boards quarterly and delete the ones nobody uses. They also don't sync across workspaces. A saved board you build in the engineering workspace is invisible from the marketing workspace even if both pull from the same underlying data. I've had people complain that their saved board "disappeared" when they switched tabs, not realizing it only existed in the other workspace. Another limitation: you can't export a saved board configuration and import it elsewhere. If you need to replicate a board setup across multiple projects, you have to rebuild it by hand. There's no bulk action for this. It's a deliberate design choice, probably to prevent configuration drift, but it makes onboarding new team members tedious if they all need the same views. For teams that outgrow this, the alternative is building custom dashboards through the API or using the project templates feature, which lets you bake a full board setup into a reusable project schema. It's more work to set up but scales better once you're past twenty people.