From time to time you have a build ID and want to open its detail in Copr. You have several options how to do it:

1. Avoid it by not exchanging build ID with your peers, but rather URL to it, because it is pain to search the a ID in Copr
2. Ask for a project in which it was built
3. Know the code and be aware of https://<frontend>/coprs/build/<build_id> route
4. Click to a whatever build you find in the recent builds box or elsewhere and rewrite the build ID in the URL. Then you will get a page Build <build_id> doesn't belong to this project. You can go to <owner>/<project> /build/<build_id> to see this build. with a clickable link to the desired build. Since I was not aware of option 3, I was doing this for years.

I think that we should enhance our search box to work with build IDs. Look at the bugzilla.redhat.com as an example. If you search some text, a table with matched results is returned, however if a bug ID is searched, you are automatically redirected to the bug detail. We can do this same way for our builds (if searched value is int and there is build.id with such value in the database). Or we can put it as the first result in the results table. This would when you have some number in the project name and want to search the project just by it. I think that both implementations are useful and I don't have a strong preference for one of them.