AKA tracking time for multiple assignees on a single task?
In ClickUp, using their “Sprint Points” field, User A and User B can both set unique values that are only associated to them even though it’s a single field. It’s essentially how we do time/effort tracking. I can then use that field to know how much effort was put towards a task overall (Sum of all “Sprint Points” on Task A) as well as individually (“Sprint Points” per assignee on Task A).
Is there a way to do this in Fibery that is somewhat streamlined? It’s such a core part of my production team’s daily workflow and I’m nervous that increasing friction compared to what they’re used to will lead to missed/lazy and therefore inaccurate effort tracking.
What exactly are your databases and how are they related?
Is it Sprint → Tasks ←→ Users ?
It is possible to create a ‘User-Task’ database with a number field, where each entity corresponds to the intersection of User and Task.
The optimal implementation of a solution depends on what view(s) you & your colleagues spend most of your time in.
For example, when looking at a Sprint entity, you can configure the relation view for Tasks as a grid view with nested User-Tasks where users can edit the points values.
Ok, I read some of your time tracking documentation (How to Track Time with Fibery) a bit deeper and have been able to recreate this with the “Bonus Solution” concept at the bottom of that page. It technically works, but it’s a bit clunky to have to use another entity. I’ll try to sell it to our team though!
In the relation view for the Subtasks, I have used a grid view showing (self-related) Tasks, and the ‘Points per user’ entities underneath:
Now, for each Task you can see who has assigned what points and also see this for Subtasks (and subsubtasks!)
I also added the formula for the total number of points (but I called it ‘Points’ so that it shows up in the grid view in the same column as the manually-added values).
If you want to make life easier for people, you can use a relation filter to limit the options when picking the user for assigning points, so that only users assigned to the task can be chosen:
Or you could work the other way around and automatically assign a user to the task if they have allocated points to it.