# Unique values per assignee on a single number field?

**URL:** <https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401>\
**Category:** Get Help\
**Created:** [November 13, 2023, 2:12pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401 "2023-11-13T14:12:04Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [November 13, 2023, 2:12pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/1 "2023-11-13T14:12:04Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 13, 2023, 2:55pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/2 "2023-11-13T14:55:22Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [November 13, 2023, 6:34pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/3 "2023-11-13T18:34:51Z")

</div>

Essentially, we have:

Releases → Tasks (with “Points” field) ↔ User  
and  
Sprints ↔ Releases

Ideally on the Task view, the single “Points” field would have a unique value per user:

Task A (3 Points)

- User 1 (2 Points)
- User 2 (1 Point)

Does that make sense?

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 13, 2023, 7:28pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/4 "2023-11-13T19:28:32Z")

</div>

> [@interr0bangr](#):
>
> Ideally on the Task view

Do you mean the entity view for a given Task, or some data view that shows multiple Tasks?

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [November 13, 2023, 8:58pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/5 "2023-11-13T20:58:57Z")

</div>

Here’s how ClickUp does it:

 ![clickup_points_per_person](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/12a9d0eb153a18bcc0349bcb847f2d83c9f61adc.png)

and here’s how/where I’d like to do it in Fibery:

 ![fibery_points_per_person](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/06a2b5d502af4ae382d6c1928d4ebf6c415677ef.png)

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [November 13, 2023, 10:51pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/6 "2023-11-13T22:51:04Z")

</div>

Ok, I read some of your time tracking documentation ([How to Track Time with Fibery](https://fibery.io/blog/time-tracking/)) 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!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 14, 2023, 10:38am UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/7 "2023-11-14T10:38:09Z")

</div>

I’m not sure how you ended up doing it, but here’s what I would recommend:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/630f9e68c366fb683992bf3c7325e66205810fd3.png)

Each Task has a collection field, called ‘Points per user’ which is a to-many relation to a database that looks like this:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3949031686c1e9f1690b8e30a94ee9f110003ced.png)

In the relation view for the Subtasks, I have used a grid view showing (self-related) Tasks, and the ‘Points per user’ entities underneath:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dcd775137afa63264d28fa47e4df5805bd007f87.png)

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

![firefox_jTySlp4R66](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b2bba50378ee961a73326ef0b94942bc0d3511d7.gif)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 14, 2023, 10:45am UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/8 "2023-11-14T10:45:48Z")

</div>

It also means you can look at a User entity and see how many points they are spending on the different tasks:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/56080db558df4efdaefa4a657c18dc6b1d3786b7.png)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 14, 2023, 10:49am UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/9 "2023-11-14T10:49:41Z")

</div>

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:  
 ![firefox_XDYapwbxzD](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/15403db581ecb44ae7fd844934ddf571052003b3.gif)

Or you could work the other way around and automatically assign a user to the task if they have allocated points to it.

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [November 16, 2023, 3:15pm UTC](https://community.fibery.io/t/unique-values-per-assignee-on-a-single-number-field/5401/10 "2023-11-16T15:15:31Z")

</div>

Very helpful, thank Chris. I had it setup similarly to how you recommended it, but the extra context and tips are appreciated.
