Is there a way to Require both Location AND Company dropdowns?

At our company we have several different companies that reside at singular locations. I have searched the THWACK up and down and cannot find any info, but is there any way that I can require not only the Location dropdown within the "Details" section of our tickets but ALSO require a Company Dropdown in that same section?

Find more posts tagged with

details

requirements

company

location

whd

Accepted answers

All comments

jhoag_gcsd

@JasonHoopingarner wouldn't that be nifty? I also would like the system to look at the "Web Help Desk Location" section of client records, and in situations where the client has "Other Rooms" listed - force the person who creates the ticket, to choose a LOCATION instead of just defaulting to the one that's listed as the PRIMARY location:

That's because in in situations where someone has more than one "Location" it suggests that they could be in any one of the locations listed on any given day (some of our staff float about in the organization and are in different buildings each day). The way the system works today? It's as if the developers put in the "Other Rooms" feature and then quit.

After that happened? Nobody else on the development team took notice of this GREAT feature, and incorporated it into the rest of the product. To that end, I've created the following feature request that includes both YOUR idea and MINE together...as I think it's the same concept...yours just being "COMPANIES" (one person could work for multiple companies).

[mention:4a0d2601069f41b59abc5d893db78e3c:fb5d84b10a5745448a7a45dafc1faa43:label=When%20Customers%20Have%20More%20than%20One%20%26quot%3BLocation%26quot%3B%20Prompt%20to%20Select%20One%20on%20Ticket%20Creation]

If you like the IDEA above, please vote for it!

pabely

I think that Locations would normally come from AD or LDAP record so are a 1:1 relationship with Client.

jhoag_gcsd

Sure and that's what the "Primary Location" is set to. But you if manually program in "Other Rooms" like we do? Nothing becomes of that data and it's basically "hidden" anywhere else in the application. The idea as described, makes the product much more verbose for customers whom have multiple employees who aren't tied directly to just one location all day.