Jump to content

Remus Avram

Members
  • Posts

    493
  • Joined

  • Days Won

    13

Posts posted by Remus Avram

  1. On 7/11/2017 at 9:20 AM, Mattias Lagergren said:

    Hi Remus, thank you for the request - we are already considering this (follow/unfollow) as part of a future change to the notifications feature. I will make sure to incorporate this information any future research

    Hi @Mattias Lagergren

    is there any update regarding this?

    If not, is there any workaround for the moment? Like would it be possible to create an action which the user triggers on a ftrack object to subscribe to it?

     

    As an example, an animation supervisor would like to subscribe to all the animation tasks from a show in order to receive a notification for each version published linked to the animation task.

  2. 21 hours ago, JPrydz said:

    Hi Remus,

    Yes, you should be able to this on Overview tab.
    Create a "Cross-project view", set a name and choose Object as type.
    You can then add "Object type" and filter on that.
    Hope this helps.

    Regards,
    Johan

    Hi @JPrydz

    thanks for the quick answer.

    The new Overview looks a bit different and the left panel (with the sequences, shots, etc) is missing. So for example you can not just select a sequence and get the tasks and milestones only from that sequence.

    Another issue is that the dashboard will display the tasks and milestones from all the projects. A way is to manually exclude all the projects which we are not interested. (It seems that it's also a bug as it displays the tasks from excluded projects as well. Ftrack version: 4.1.5.4750)

    Best,
    Remus

  3. 3 hours ago, Mattias Lagergren said:

    No updates as of now - as an additional workaround, have you looked into writing a message (note without parent) to the user? This should trigger a notification

    
    note = session.create('Note', { 'content': 'hey', 'user_id': author_user_id})
    sesssion.create('Recipient', { 'note_id': note['id'], 'resource_id': target_user_id })
    session.commit()

     

    I think this is what exactly we are looking for :) 

    we will give it a try and let you know if works for us

  4. At the moment I don't think it's possible.

    We would like to be able to have custom attributes per asset type also. Another example is that we have the camera published in Ftrack and some specific custom attributes like `shutter_open` and `shutter_closed`. These custom attributes should not be visible on a different asset type.

    For each asset type there are specific custom attributes.

  5. 11 minutes ago, Martin Pengelly-Phillips said:

    Note that you could also write your own cache interface to connect to a shared cache if you want to reduce DB hits. For example, we run a Redis cache per site and created a RedisCache implementation as a subclass of ftrack_api.cache.Cache.

     

    Thanks for the info! We will try to test this, too.

×
×
  • Create New...