Mattias Lagergren
-
Posts
1,083 -
Joined
-
Last visited
-
Days Won
90
Content Type
Events
Profiles
Forums
Downloads
Everything posted by Mattias Lagergren
-
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".
-
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? Thank you for highlighting this. The ftrack.validate event is deprecated and we will make sure to remove it from the documentation.
-
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
-
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()
-
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
-
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()
-
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). -
I'm afraid it is not possible to filter on different object types with an ANY condition
-
Cool, no worries and thank you for following up!
-
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.
-
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?
Mattias Lagergren replied to vitek's topic in API
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
Mattias Lagergren replied to INFECTED's topic in General discussion
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
Mattias Lagergren replied to INFECTED's topic in General discussion
I think that are two purposes: For communication; to keep track of that the object (and containing tasks) should be tackled by the users in the allocated group. The user selector when assigning tasks are restricted to the users in that group. This makes sense and is something that we've discussed internally but never got to investigate further. -
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.
-
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)
-
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
Mattias Lagergren replied to Robinson's topic in General discussion
Hi, I will forward this feature request to the team -
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.
-
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).
-
Hi, thank you for this input. I will forward this feedback to the team for future considerations.
-
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.
-
Ah, almost - I'm afraid you would still need to create a new session per thread.
-
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.
-
It is not something that we are actively working on right now but I will raise this with the team
