We're in the middle of a classic>Lightning migration. Just discovered that quick actions on the Case object work differently than they do on any other custom object. Rather than displaying a button at the top of the page to click to execute them, they show up as a tab in the Chatter publisher. All of our Javascript buttons were converted that executed VF pages, as well as a couple related list buttons.
Disabling feed-tracking for Case isn't an option, and the UI with selecting a tab in the chatter publisher which then pops a page open is a terrible solution. Why can't this just work like every other object? What have others done? Can anyone point me to documentation about the case object in lightning working differently?
@Pranav Nagrecha Thanks! For us, we have a sorta complicated ticket close wizard that was a Visualforce page. It definitely could use re-writing as a lightning Component to make it more user friendly, but I don't think it would be something we would want on the page all the time. Popping it up on in a modal from a button would be the ideal scenario. Rendering it within the chatter tab would look awful. With all the other lightning conversion tasks re-writing a complicated UI is a lot more involved than fixing the js redirection on save, or simply converting a JS button.
