1 person found this helpful
Reviewing through your description, you might be running into an issue being tracked as JIVE-75651, which is set to be resolved starting in the 2016.2 maintenance release scheduled for this week. However, if you would like to confirm or if you continue to see this behavior after the maintenance update this week I would recommend submitting a case in your customer group here in the Jive Community for additional investigation into the behavior by the next available member of our support team.
I tested now that we got the latest maintenance release and this is now working!!!