Shotrunner sent Email Headers

Yannick Meillier's Avatar

Yannick Meillier

22 Oct, 2009 03:49 PM via web

This is to follow up on a discussion i had with cameron.

when involved indifferent projects ran through shotrunner, all not ification emails start with
[shotrunner] discussion [shotrunner] reply to....

would be nice if the name of the project would be included in the brackets:
[shotrunner - project name]

this way we can redirect those emails directly into theri appropriate folders for email organization.
right now , kind of mess if involved in multiple projects....

not saying that the header could be renamed at will. just use the project name/shotrunner project ID.

-yannick

  1. Support Staff 2 Posted by cameron on 23 Oct, 2009 05:00 AM

    cameron's Avatar

    Hi Yannick,

    I'm thinking that we need to introduce an account parameter that would be the the text that goes in between the brackets. I'm guessing that different accounts will want different combinations of:

    • Account name or studio name (e.g. "fxphd")
    • Project name or code (e.g. MD or Moving Day)
    • "ShotRunner"

    Or, Maybe I could just do "ShotRunner" and the project ID as this is generally pretty short (now I see this is what you suggested!)

    So it would be:

    "[ShotRunner-MD] Some Topic"

    How does that sound?

    --Cameron

  2. 3 Posted by Yannick Meillier on 23 Oct, 2009 08:12 AM

    Yannick Meillier's Avatar

    Hi cameron.

    >> Or, Maybe I could just do "ShotRunner" and the project ID as this is
    generally pretty short (now I see this is what you suggested!)

    Exactly, this is what i had in mind. I'd assume that whenever someone starts
    a project with shotrunner, they have to pick a project ID anyway and that ID
    is hardwired.

    Adding the project ID inside the brackets [shotrunner - project_name] would
    be great to sort out the multiple emails we get from different projects
    managed by shotrunner.

    Ultimately, i was thinking that there should be some kind of
    hierarchy/convnetion follwing the first square brackets. to sort emails into
    folders for specific shots. sequences.

    like:
    [shotrunner - project_name] [Seq.1] [Shot.1] Re: comment on....
    [shotrunner - project_name] [Forum] Re: comment on....
    ...

    take care.

    -yannick

    On Fri, Oct 23, 2009 at 7:00 AM, cameron <
    tender+d94777fe9cd9e6a2700320a54b552ee7f28a3b08c@tenderapp.com<tender%2Bd94777fe9cd9e6a2700320a54b552ee7f28a3b08c@tenderapp.com>
    > wrote:

  3. Support Staff 4 Posted by cameron on 23 Oct, 2009 01:32 PM

    cameron's Avatar

    Yannick,

    I just realized something: The whole point of using ShotRunner for
    team communications rather than email is so that you *don't* have to
    save all your emails, respond to emails, and wonder where to file
    stuff. The benefits of ShotRunner over email are:

    1. All communications between team members are logged in a central
    place.
    2. The communications are organized into the project hierarchy.
    3. All of the history is right there, with the shot, element, task, etc.
    4. You can search through all of the communications history.
    5. Communications can be flagged for follow-up via Request Response.

    I use both ShotRunner and Basecamp on various projects and I *never*
    save the notification emails. There is no need to because I know that
    everything is safely filed away under the project.

    Also, you can always view "What's New" on the project overview, and,
    if you go back to your dashboard, you can even see all of your email
    notifications if you need to.

    What do you think? Do you still want to bother with emails?

    Cheers,
    Cameron

  4. 5 Posted by Yannick Meillier on 25 Oct, 2009 08:06 PM

    Yannick Meillier's Avatar

    Hi cameron.

    yes you're right, shotrunner is the place where everything gets archived so
    no need to archive everything on my email client.
    Still it would be nice to at least have the header include the project name
    to differentiate email updates from various projects.

    Also, i just had an idea.
     you know that thread mike started to post his daily podcasts at? maybe i
    wasn't supposed to post anything there, even comments.
    so it might be nice to set permissions to prevent people from posting. so
    that a thread canstay clean.
    i remember in red dwarf where we used basecamp, we had the same issue where
    simon had created a thread for him to post only and poeple would post there.
    so would be niceto set permissions in forum threads to prevent that from
    happening.

    -yannick.

    On Fri, Oct 23, 2009 at 3:32 PM, cameron <
    tender+d94777fe9cd9e6a2700320a54b552ee7f28a3b08c@tenderapp.com<tender%2Bd94777fe9cd9e6a2700320a54b552ee7f28a3b08c@tenderapp.com>
    > wrote:

  5. Support Staff 6 Posted by cameron on 25 Oct, 2009 08:11 PM

    cameron's Avatar

    Hi Yannick,

    Yes, I think that is a good idea -- sort of an 'announcements only'
    forum, or moderated topics.

    Also, people have been asking for 'sticky' topics that stay at the
    top. I will think about how to do both of these things. We are
    currently redesigning some aspects of the forums.

    Cheers,
    Cameron

  6. Support Staff 7 Posted by cameron on 15 Nov, 2009 08:53 PM

    cameron's Avatar

    Yannick, FYI, John Montgomery made a similar suggestion, so we are going to be improving the email headers. (Mostly because now I know what to do.)
    Cheers,
    Cameron

Reply to this discussion

Internal reply

Formatting help or Preview

Attached Files

You can attach files up to 10MB

Ten divided by two is what?

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.