13
votes

I have, out of curiosity I guess, clicked the little grey 'x' to the right of a project on my TeamCity Project Dashboard. It turns out that it hides the project from the dashboard.

And now I cannot find a way to 'unhide' it. When I try to use Configure Visible Projects menu, it says it's visible. Also if I hover over the downward arrow next to the Project link in the menu, I can navigate to the project.

But I really want to see it on the dashboard again.

Thanks.

3
And just as I post this I find the solution. Turns out it was the Build configuration that was hidden, and not the actual project. Configuring the that to be visible solved it. - AndersDaniel

3 Answers

31
votes

For those (like me) who struggled to find the configuration alluded to above:

  1. Go to the main page (with the list of projects).
  2. To the right of the project with the hidden build config there is a drop down that says "1 hidden". Use that to unhide it.
1
votes

As a hack, you can get the request that's normally made to show a build configuration, but using a network console in the browser. You can (e.g.) install the Postman REST API client for Chrome and make that request manually, with the parameters for the build configuration that went missing.

POST to https://example.com/visibleBuildTypes.html with these parameters:

projectId=YOUR_PROJECT_ID bt_visible:btXX (where XX must be replaced with the internal ID for the build configuration) showOne:true (as opposed to hideOne:false to hide it)

ref: https://youtrack.jetbrains.com/issue/TW-16794

1
votes

If you are hitting this from google in 2016 (or later...) like I did, this is a bug that has returned and the answer above doesn't help (unless maybe you are still on an ancient version of TeamCity).

To fix:

"... Go straight to the project page. Add a (temporary) build configuration. Go back to the overview page, and the project should be visible. Now go to the down arrow next to the project name and unhide each of the build configurations. Remove your (temporary) build configuration."

We are running on 9.1.1, and the above was also tested on 9.1.6.

Source: https://youtrack.jetbrains.com/issue/TW-44218

Seems to be fixed if you upgrade to TeamCity 10.0.