Open Discussion-What Makes a Great Communication & Notification Experience with Shotgun

Hi Community,

I’m starting the thread here for open discussion- what makes a great communication and notification experience with Shotgun.

We now have SG inbox, email notification and Desktop notification of browser. Any feedback on these feature? Yay, I hear yo!

  • A push to instant message app when certain event triggered on Shotgun(You could achieve this with self development via Shotgun API).
  • Filter SG inbox message with certain fields (to , cc)-thanks doc for sharing your wisdom here.
  • A grid page of all my Follow entities, to configure fields I would like to follow and get notified or unfollow
  • Get notified on field update of linked entities of the entity I followed (e.g. get notified on tasks status update when I follow an asset or a shot.)

Anything else? Do not hesitate to help shape the future communication and notification of Shotgun with us.

Cheers,
Ben

6 Likes

Good topic Ben, thanks for starting the discussion!

The top request I hear is the desire to customize the format / layout of the Inbox email notifications. We provide some ability to do this with the legacy notifications, but there is regularly a need to adjust what fields are displayed, or how information is presented, in the subject and body of the notifications generated by following and the :inbox_tray:.

A digest feature would be great too - option to get a summary of the updates over a certain time period, rather than each notification coming in with every update. That can get overwhelming pretty quickly.

If any of these requests resonate with you, or if you have other ideas for making notifications work really well in Shotgun, please chime in with your own use cases or suggestions! I always like to hear if you have used another piece of software that handles notifications really well. I’m guessing Facebook is not it. :poop:

2 Likes

Scripting access would be a big plus. We have some scripts that posts notes or replies to inform people of things. But it’d be a lot neater if we didn’t need to post actual notes or replies that clutter up activity streams.

It could also help with people who get too many notifications, and want to tidy up their inbox. eg. There’s a long standing bug with Task Templates that sends notifications to users assigned to those tasks even if they’re not subscribed to those updates. We could script a fix to just mark those as read if we had access.

I think the biggest problem we have is with people not reading their inboxes, and it’s easy to see why some people wouldn’t keep Inbox zero when it can easily jump up to 99+ in an instant.

3 Likes

We’ve been doing this with a Slack Bot for the Tickets when the Status changes and with new replies and it works really well.

2 Likes

Excellent topic!

Hope this reply isn’t too dark. Apologies. It’s just the nature of our struggle :wink:

I have not been able to provide an effective notification system using Shotgun:

  • we don’t use desktop, so it’s “keep your browser open” (which is too much to do)
  • not everyone opens up Shotgun, some, never
  • all Inboxes are at 99+
  • email is the ‘single source of truth’
  • nobody has taken the steps to ensure that desktop notifications are enabled
  • I have to physically go to each desk to show them
  • it stops after a while, and rinse-repeat, and hence, it’s unreliable

Another problem is the unsatisfied need to have the notifications triggered by systems outside the realm of Shotgun, or, that the notifications are controlled by logic outside – so – in effect – the notifications need to be cross-system.

Specific example: the batch queuing system (farm) is not connected to Shotgun currently, and is an important contributor to events. Redis does the pub-sub’s for the farm.

The point I’m making is that unless all your production systems are completely tied to Shotgun you can’t get effective, real time notifications – at least you can’t convince crews that it’s a Killer App – the only thing that makes productions willing to change to a new way-of-doing-things.

Notifications have to be managed by a cross-systems aggregator, eg. redis, or rabbitmq… or hooks… or…? It’s all too alpha at this stage.

I’m looking into Shotgun-trigger nodes for n8n – meaning, Shotgun will end up being slaved to some other “event management.”

Also tried exercising Mattermost (in liu of Slack) but I’m not convinced anybody wants yet-another-communication-collaboration-system. After all…

I hate email… it’s Shotgun Kryptonite.

This all ties back to… One needs a Production Single Source of Truth

Looking forward to more wisdom from others on this topic! Happy Friday.

2 Likes

This thread starts to feel like an AA support group, haha
And it feels good, thanks Doug :wink:

Yeap, email sucks, but we are using some Custom Threaded Entities that aren’t tied to the Inbox, just like the Tickets.

2 Likes

Truth.

2 Likes