1

Multiple Project Templates

Is there a practical application to the "Project Type" field?

We could really use multiple project templates in our workflow.   One for live action and vfx.  One for motion graphics.  One for 3d animation.   Also we are looking at how we might use shotgun as well with scripting and development projects.   All of which will use pretty different default setups.   A drop down of "VFX Template, Game Template" etc would streamline job creation.

10 条评论

  • 0
    Avatar
    Stu Aitken
    I'll second that one - types matching to specific type templates seems like an obvious addition to the project creation features and is something we would also use a lot Of course you can just duplicate a project which is a good way of doing something similar currently
  • 0
    Avatar
    Gavin Greenwalt

    Ha! Duplicate a project.  Excellent tip!   After all that's pretty much the built in approach anyway. 

  • 0
    Avatar
    Gavin Greenwalt

    Is there a way to hide a job from the projects list? Like a template job?  So that it can't even be viewed? Like the template job?  

    I tried setting its status to no status like the template project but that didn't work.

  • 0
    Avatar
    KP

    Gavin,

    If you haven't already discovered this, we have the ability to control what Projects are seen using our permissions framework. Artists can be limited only to Projects they are linked to. Other projects won't even show up in the left nav. Even if they follow a link to a page in a Project they aren't linked to, they will be given a friendly error page. Check out the docs here https://shotgunsoftware.zendesk.com/forums/32075/entries/38733

  • 0
    Avatar
    Ryan Mayeda

    Being able to make multiple project templates based on type would be nice.  This would help stifle the complaints from our Commercials people that they get a bunch of Features-centric pages when their projects are created.

    Related question, is it possible to create a new project and then give it specific pages, that may or may not be in the template project, through the API?  Maybe that's a reasonable workaround for the time being...

    Ryan.

  • 0
    Avatar
    Sam Bourne

    I also would find Project Templates or something similar to be very helpful. Right now we have a list of different type of projects in the "Type" field. An idea would be that this field could link to a Project Template. So you create a project, tell it what type of project it is, then it creates pages accordingly. I'm not sure how to manage the Project Templates, and having a default one would still be important for new project types.

  • 0
    Avatar
    Stu Aitken

    we've been setting up a couple of different types of projects just recently and I have been thinking that also having optional entity fields per project tpe would ve very useful as well

     

    eg if we are doing a commercial the asset and shot information we need to track is often quite different from say agame cutscene project

    at the moment adding fields to the same entities across both project types is getting messy and having some kind of better encapsulation of entities according to the project type would feel a lot neater (and safer)

    I'm guessing this would require some fairly fundamental changes to the way shotgun deals with the underlying schema and certainly there are several fields that would be considered pretty much 'communal' across all project types but having the ability to say entities have these optional fields on project type A and a different set on project type B would be very useful indeed

  • 0
    Avatar
    Isaac Reuben

    We will be opening up more page-related functionality through the API soon, so should be possible to copy around pages.

    Currently you can right click on a project in the left nav, and duplicate it, which is *kind of* like having multiple project templates, but not quite as satisfying.  We're planning to have project creation be more wizard-like, where you create the project, choose a name and a template (can clone any existing project settings), and assign people to it.

    It's also on the list to be able to cull the list of fields per project.  The goal is to limit the number of fields seen for each entity, but still make sure that people are re-using the same fields across projects where it makes sense.  There would still be one global list of fields, but each project could set the fields it *doesn't* want to use, so they just wouldn't show in any of the menus and dialogs within that project.  These visibility settings would go with the project template of course, so you when you clone a project the new one would have the right fields.

    How does all that sound?

  • 0
    Avatar
    Stu Aitken

    sounds better :)

     

     

  • 0
    Avatar
    Gavin Greenwalt

    I believe you can mark this request as Done. 

请先登录再写评论。