Search and/or quick access cards by their card number.

[demirelio]

In my team we loved how clean the id numbers are and most of the times we reference tasks with their numbers in our chats or in other cards.

But we can't search cards by number. That'd be great if we could Search(K) -> #number -> Enter -> See/Go card

What's interesting is, this actually works in:

1. Card Content Area
2. Card Comments

But it doesn't work in:

1. Card checklists
2. Search area

---

Currently we quick access cards by clicking a random card and change the card number in the url in our team.

[janrenz]

Currently there seems to be no easy way to open a card by entering the ticket number. The search can search for the internal card id, but not for the number (the one that is displayed in then UI). I see to options: Either a new top level keyboard short cut like "o" or extending the search.

Also there are different options, we could extend the search index by the number or add a special syntax in the search bar, for example if you enter "#" followed by the number it could directly open the card.

Let me know what would be prefered, i am happy to open a PR.

Prototype.number.search.mov

[demirelio]

I think the best and easiest ux is:

1. User search and types #[number] it activates dropdown to show matched cards by their id number.
2. if user taps enter it takes user to that card with the number(or the top result in the dropdown)

i think it should be:

1. @ symbol is for people

2. is for card ids or maybe card + project ids to easily access and move between boards and tasks

3. / is for file and all other references.

[rtharston]

My team uses Fizzy in our daily standup and we run into this same issue nearly every meeting. I've also resorted to the same workaround of clicking a random card and then changing the URL.

This morning one of the people on the team joked to say this works now and the person running the meeting believed him so he went to the search and put in the card number but it only showed the cards that refer to that card in the description.

[Michoels]

Would love this!
It's sorely needed.

As a workaround I made a Raycast quicklink that takes card number, assembles the card URL, and opens the card in my browser.

[mitchplze]

Not sure what the point of the #'s is, if there is literally no way to search for them!

We need this feature for sure. I'm a fan of the # hotkey, type ID, hit enter.

[jimmystuart]

Figured I would bump this by saying that searching for a card number would be huge for us. We're using this as the owner in a building project and are creating a card for each item for our architect and we're including that card number on the drawings themselves. We're then giving our architect read-only access and would love for them to pull up cards directly for more info.

[mitchplze]

Doesn't seem like the devs are interested in adding features, or reading user feedback. The lack of the ability to call up cards by their unique ID number, make this project completely non-viable for many situations.

[dsbowman]

Adding the Koble Systems angle here, since it's a bit different from the standup case @rtharston described above.

We have multiple teams and several different actors working across the same boards. The card number has become the one reference that travels everywhere — it gets said out loud in meetings, typed into chat, and quoted in threads with people who don't have the card open in front of them. That's the whole value of a short numeric ID: you can hand someone a reference without having to pass a link, and it survives being repeated across tools and conversations that Fizzy isn't part of.

Which is what makes the gap awkward. The number is the identifier everyone actually uses, and it's the one thing you can't put into search. Today the answer to "pull up 847" is still "open any card and edit the URL."

On the design question raised earlier in the thread, I'd argue for keeping it narrow:

• #847 in search → jump straight to card 847
• bare 847 → unchanged, keeps searching card content

That preserves searching for numeric content inside cards, which we'd lose if bare numbers were treated as IDs. It's also the smallest change that solves the problem, and it doesn't foreclose anything — a match dropdown or a global hotkey can still be layered on later without contradicting it.

#2665 already implements exactly this behavior: two files, tests included, currently mergeable. Per CONTRIBUTING.md, though, feature work moves to the issue tracker once it's actionable and well-understood, and this discussion was never promoted — so that PR has nothing to land against and has been sitting unreviewed since March.

Would the team be open to promoting this to an issue so the PR has a home? Happy to help test it against a real multi-team workload if that's useful.

[flavorjones]

Hey all, sorry for the wait on a fix for this. It turns out this used to work as expected before we converted to UUIDv7 card ids at the last minute before release. 😮‍💨

So I've adopted @janrenz's PR #2665 with a slight simplification: just the bare card number will look up the card:

screenrecording-2026-09-10_11-31-15.mp4

And if you want to continue to search by card content, then you can just wrap it in quotes:

screenrecording-2026-09-10_11-31-39.mp4

Deploying to app.fizzy.do now!