[Bid days column incorrect until expanded]

Hi! I agree and can see that this is confusing. We will look into clarifying what is happening; for larger projects the bid, worked, +/-, status progress and other columns are not actually loaded until you expand something. This is for performance reasons but does also impact the summaries.

We will see if we can make this clear and show something else instead of "0.0".

[Enforcing project and shot naming convention?]

Hi and thank you all for your feedback. We understand the motivation for validating input and will take this into consideration for future development. As I understand it and what I've heard from other customers is that the project code, but also shot / asset / task names should be validated.

A suggestion in the first post is to have a regexp to control this, what do you think about this? Would that be enough for your use-cases?

 

Quote

I'm a bit confused as to the the ftrack.validate event subscription seems to remain in the documentation. I won't have a chance to test this for a while, but Project Code validation is a huge need for us, and the current docs seem to indicate this is possible...?
https://help.ftrack.com/en/articles/1040479-events
Scrolling to the bottom, I see the ftrack.validate topic listed. Are we saying if I set up an event listener for this topic I won't get anything?

Thank you for highlighting this. The ftrack.validate event is deprecated and we will make sure to remove it from the documentation.

[Subscribe to a Ftrack object]

Hi Remus, as of now it is not possible to do this but using the API and event listeners you could achieve a workaround to achieve what you are looking for.

E.g. listening to ftrack.update events for when a new asset is published and sending a Message to the supervisor. The message can pop up in the Inbox or sent as a mail. Let me know if you want to work in this direction and if I can help you more

[send custom notifications via ftrack_api]

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()

 

[in-task checklists]

Remus, no checklist/todos has been implemented - the closes thing is what you've found regarding note completion. But this more related to feedback and seeing if it has been addressed or not

[Removing a component from a Note]

Hi,

With the code you have there you are only removing the component file from the server location.

Instead, try to remove the component itself:

session.delete(component)

session.commit()

 

[Advanced filter settings: "Any" condition for all entity types]

It is true as you say, Task, Milestone (and other object types) are modelled as tasks in the backend. But for filtering we are locking a filter to a specific object type and as of now it is not possible to mix them with an ANY condition.

We're currently developing a new view where you can list items from different projects (to be released within a few months). One of the use-cases that we consider is similar to the one you mentioned here, so listing Milestones and Tasks together with a filter like that could be possible (but it is still under development so not set in stone).

[Advanced filter settings: "Any" condition for all entity types]

I'm afraid it is not possible to filter on different object types with an ANY condition

[not able to jump back to the first frame if frameIn not -1]

Cool, no worries and thank you for following up! 

[not able to jump back to the first frame if frameIn not -1]

Remus, is this for in the internal ftrack review or the client review? If in internal, is it when you put them in sequence? 

At the moment we are not able to reproduce this.

[not able to jump back to the first frame if frameIn not -1]

Thank you for reporting this, I will raise this as a bug with the team

[How to make publish look like published by another user?]

When you create the AssetVersion from the API you should be able to set the 'user_id' to another user:

version = session.create('AssetVersion', {'asset_id': asset_id, 'user_id': another_user_id})

 

[Assigning user groups to objects]

On 6/1/2018 at 10:05 AM, INFECTED said:

In a large project Producers or Lead artist don't necessarily need to assign all tasks to a specific user. The freedom of saying for example these are alle the 3D modelling tasks and i assign them to the 3D modelers group seems very nice.  These tasks then appear under the 'available task' column in the my task view for everyone in this group and if a 3D modeler drags a task to another column 'in progress' for example it gets assigned to him/her directly and disappears from the 'available task column for everyone else. So they just work through the pile as they like.

Makes sense, would the 3d modellers group in this case be a group on that project? I.e. a subset of all 3d modellers in the Studio, that are now working on this project

[Assigning user groups to objects]

I think that are two purposes:

1. For communication; to keep track of that the object (and containing tasks) should be tackled by the users in the allocated group.
2. The user selector when assigning tasks are restricted to the users in that group.

Quote

Btw. Our Producer all thought that this would assign all the task inside the object to all the users in the group or make the task available to them and they can select task from the object themselves and i actually think that's a good idea?!

This makes sense and is something that we've discussed internally but never got to investigate further.

[Time logging]

On 5/24/2018 at 2:25 AM, kristing said:

Currently the timesheet/time logger views allow you to select a Milestone in the Tasks drop-down if you are assigned to it. Given Milestones don't have "Log time" or "Show logged time" in their More menu, it seems as though this is a bug. If it's not, it would be useful to be able to designate what entities a user may log time to -- Task, Milestone, Shot, etc -- to have more control of timelogs.

Thank you for reporting, I was not aware of this and at the moment we've restricted time-logging to task and this sounds like a bug.

[dynamic enumerator and current selection]

Hi Tim,

Sorry for the confusion on this - you're correct, the id is wrong when accessed from the sidebar. To work around this you can do the following:

if '_' in entityId
	realId, junk = entityId.split('_')

As for the entityType - this is old style entity type from the backend. Instead of using 'task' you would want to use 'TypedContext' on the session:

session.get('TypedContext', realId)

 

[Parent attributes available on Child]

Hi Ozen, I remember us discussing this and we're tracking a feature request about it. I will forward this to the team

[Limiting a Custom Attribute to Specific Asset Types]

Hi, I will forward this feature request to the team

[Flame integration]

Hi Jerome, we have hidden it from bitbucket because it is not officially support / maintained. If you want I can give you access - please email support@ftrack.com and refer to this thread.

[Creating new events using API]

To attach a calendar event to a user you will want to create a CalendarEventResource with the calendar_event_id and resource_id (the id of the user).

[mobile version need work]

Hi, thank you for this input. I will forward this feedback to the team for future considerations.

[Project Creation Dialog]

Hi Tim, may I ask what the reason is for overriding the whole dialog? Sometimes it is enough to listen to project creation and pop up an Action UI with additional information that should be entered.

[ftrack_api threadsafe]

Ah, almost -  I'm afraid you would still need to create a new session per thread.

[ftrack_api threadsafe]

One possible way to move forward with this is to change the example above and pass in the project id to the threads and then query for TypedContext where project_id is <project_id> in the thread.

[ftrack_api threadsafe]

22 hours ago, Remus Avram said:

ahh... are you going to make it thread safe?

It is not something that we are actively working on right now but I will raise this with the team