We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Comments
Bump... Please vote for this. Bit surprised this isn't more of an issue for people.
For example, currently, out of the box, we cannot even search for MAs by support group. Yes this is an extended field, however it is already somewhat "built-in" to the product via the Portal group mappings configuration etc.
The lack of this feature contributes heavily to the fact that we are turning to SSRS more than the dashboards (10:1). By the time we get a report analyst to write out the SQL to make a meaningful report, it makes sense to spend another hour to draw up the report grid so that we can get subscriptions, use params, etc.
If users could quickly create their own views and we could turn those into dashboards by using the saved searches, it would be a game changer. Search looks like an amazingly powerful tool until you see that none of the fields you want to search on are available.
To be truly powerful, relationships would need to be part of it (specify a type projection? define them as part of the search? however it needs to be done...), but extended properties would be a good start.
Ad Hoc search is the portal's biggest weakness right now, when compared with other ITSM products. It seems like it would take very little effort to turn this into a strength--just include the missing fields from extension classes and type projections. It does not even need to be automatic--let portal admins specify them, if that makes this more feasible to release.
starting on line 627 with the list of properties common to all work items.
It seems a rather simple exercise to extend the properties and relationships which can be searched by adding definitions to the appropriate sections.
N.B. Modifying this file is not supported, so if searching for an extended property or relationship does not work, or causes performance issues in the portal, you will probably have to roll back to the original version of the file.
When I add their definitions here, I can get them to show up in the dropdown list but they are not searchable. That makes sense if the search is looking at dbo.WorkItem, since none of the values I need exist there (again, I am trying to search class extension properties, and that table doesn't store any).
It appears that the search is using /search/GetAdHocResults (around 358) which in turn is reading the dbo.WorkItem table. My properties and relationships aren't in that table.
On line 366, can I specify a different table, and if so, can it be in a different DB? Or do I need to create my own from-scratch web service that knows how to utilize the filter criteria for this one?
Yes, I also updated the implementation notes above to indicate this recently. You will be able to choose the columns for a service request that can be searched.
I just upgraded to 9.1.0 but the search function seems to be the same. Am I missing something?
Links to another similar discussions:
The Global Search Feature is now available in both latest and baseline v10 releases. You can read more about it here and this KB.