Admins. As others said, it's not that easy. Especially since many of the built-in fields we don't use and have custom fields of our own, various common fields that are calculation (text mode) fields, and built-in fields with odd/unintuitive names. The users do quietly make custom views (and I often ...
Same one we received. Also, this ticket does not have the same prompt response times as is normal for Support…it takes days to hear back from anyone, so the "conversation" is taking forever. I tried to get a meeting to just get through it, but they are not scheduling meetings for this one. Honestl...
@Skye Hansen‚ We have adds/subtracts between object types as well. One interesting solution might be if the new wildcard could somehow be used with the existing show/hide functionality. So if it is a certain object type at least some fields could be added or removed via hiding/revealing. I know this...
I ran some tests in Preview to check "instanced" behavior: to verify if an Issue converted to a task or project is the same form (multi-object custom form), but a "copy" with independent data. I can confirm that, for example, you convert the Issue to a Task or Project: If you change data in the Issu...
Same here; sounded mandatory. I really don't have time to deal with this right now, can I ignore it or respond that I decline until the official effort starts?
I'm curious about how to "migrate" to cross-object custom forms too. I know we have no real plans to change/collpase the existing ones until I can test what happens. And any use of the new one has to be carefully considered. What happens if I make a cross-object, but then find I need to "separate" t...
Well, at least there is that, so I can turn down the panic-meter. But yeah, we should be able to turn off the selection. It's gets old explaining to users "yeah, they have this new feature/tool/whatsit but we turned it off/don't use it because of time/policy/etc."