[JENKINS-35414] Folders don't show up in dashboard view after upgrade

[TobiX]

After upgrading Jenkins from 1.658 to 2.7 and Dashboard View Plugin from 2.9.7 to 2.9.10, the folders do not appear in a job list created in the Dashboard View.
Steps to reproduce :

• Jenkins with Folder and Dashboard plugins
• Create a folder
• Create a dashboard view and use regular expression ".*" to include all jobs.

Playing with other filters, or manually selecting the folders to display doesn't work either.

---

Originally reported by eguerints, imported from: Folders don't show up in dashboard view after upgrade

• assignee: tgr
• status: Open
• priority: Minor
• resolution: Unresolved
• imported: 2022-10-30

[TobiX]

medianick:

Same problem here with Dashboard View 2.9.10. It doesn't seem to be related to how the jobs are chosen for the view (regular expression or explicitly chosen list via checkboxes) – neither works. I downgraded to 2.9.7, which I'd been running previously, and Folders reappeared.

[TobiX]

sirko:

Having the same the same issue. Any due dates for fix?

[TobiX]

nikomad:

Here the same bug. any news to this issue?

[TobiX]

leufkes:

please fix this

[TobiX]

piyush_jalan:

I am also facing same issue. There is an exception on dashboard and no folder is visible.

[TobiX]

brunobieri:

I experience the same issue.
After investigations I guess one of the following fixes is causing the folders to disappear:

Ensure that ${jobs} is really a Collection
evandy0@18ef513

[FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection
baa8c50

Workaround
As a temporary workaround you could check the checkbox `Recurse in subfolders` on your view and you would be able to select jobs within your `Folder` project. It also works if you use Regex for your view.

[TobiX]

shashank1592jain:

not resolved facing same problem still

[TobiX]

mmraz:

Experiencing this same issue with Dashboard View 2.10, Jenkins 2.164.1

 

I removed the Last Success Version plugin as its added column doesn't produce a working link any longer.  But, uninstalling the plugin left the default All view with the broken column.  I tried to replace the default view with a simple Job List but cannot get the nested folder structure provided by the default All view due to this issue.

 

[TobiX]

inetov:

why was this bug with priority "minor"?
this is an important problem - it is impossible to display folders on the dashboard in any convenient way.

[TobiX]

koxta19:

Same issue here with Jenkins 2.289.3 , Dashboard View 2.17 and Folders 6.16.
Folders in view are not visible after adding them in configuration.

Only if I use the "Recurse in subfolders", I can see the sub-jobs but this is not what I want.

[TobiX]

JIRAUSER142189:

We are using multibranch pipeline for GitHub pull requests. It is not possible to create a dashboard view with multibranch pipeline job. From my point of view, this issue should not be a Minor priority.

[eoc-ross]

It appears that on line 48

dashboard-view-plugin/src/main/resources/hudson/plugins/view/dashboard/Dashboard/main.jelly

Lines 47 to 49 in 8ce3933

	<j:if test="${it.isIncludeStdJobList()}">
	<t:projectView jobs="${jobs}" showViewTabs="true" columnExtensions="${it.columns}" indenter="${it.indenter}"
	itemGroup="${it.owner.itemGroup}"/>

The job list (referenced by jobs) is used. Unfortunately jobs, is filled in with instances of Job class only, whether Folder, MultiBranchPipeline and Organization Folder are not.

However, the list is only shown when selecting

So, it should be safe to assume that the "standadrd jenkins ListView" behaviour to show items instead of jobs would be fine.

I'm willing to make a PR for the fix if it's ok. Also I'd like to include some other changes:

• scheduling a new build in the other portlet has the same problem: doesn't work for item in subfolder
• make "job filters" work with subfolder (i.e.: using regex .*/master which shows only the top element in "standard jenkins view" and recursively only master branches in "Unstable jobs" portlet)

[kerrhome]

List view works for also displaying Multi-Branch Pipelines, so I'll use that, but what we wanted was to use Dashboard to take advantage of the portlets. It's too bad that this is still an open issue because Dashboard View is awesome.