# Report: Chart annotation for values not graphed
**URL:** https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529
**Category:** Get Help
**Created:** [December 13, 2023, 7:16pm UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529 "2023-12-13T19:16:23Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@lars](https://community.fibery.io/u/lars)
#### Post date: [December 13, 2023, 7:16pm UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/1 "2023-12-13T19:16:23Z")
Hey there.
I’m trying to create a chart in a report that looks like the following sketch drawing (please ignore the blue line as it’s not relevant to this question):
The data structure I’m trying to create it from is as follows:
- **Epics** (as in “sub-projects”)
Epics have two computed fields for a total estimation of duration (upper/lower bound). They don’t carry a useful time value.
- **Progress Estimations**
Progress Estimations estimate (or “guess”) the progress (0-100%) of an Epic. The database contains a timestamp, the relation to the epic (one epic has many estimations), and two (computed) values for progress, again upper and lower bounds. Note that a given set of estimations doesn’t need to cover all epics. If some epics don’t have an estimation, that is perfectly fine (counts as 0%)
Now back to the sketch: The purple and yellow lines chart the estimations at different points in time (x-axis is time), and they work nicely.
However, as these estimations have a natural upper bound (“100% completion”) I would like to add that line as an annotation to the chart. So, for a given set of epics (from the filtered source data) I would like to display the sum of all values as the 100%-annotation on the purple and yellow lines. However, the value itself does not appear in the chart (since the x-axis is time, and the epic doesn’t carry a useful time value).
I don’t seem to be able to calculate a value in an annotation that isn’t part of the actual chart. Is there a way around this? Or a different way to go about this?
Thanks in advance
Lars
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [February 19, 2024, 7:49am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/2 "2024-02-19T07:49:20Z")
Can you share some example data (here or in chat if it’s private) and we can have a look.
---
### Author:  [@lars](https://community.fibery.io/u/lars)
#### Post date: [February 21, 2024, 3:03pm UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/3 "2024-02-21T15:03:23Z")
Hey Chris,
thanks for your reply!
I’ve compiled a little sample space to hopefully make things clearer:
> **[LF - Chart Annotation Example — Fibery](https://shared.fibery.io/sign-up?appShareId=4f94d997-26f4-4a41-a5f2-0d6c363e399f-lf-chart-annotation)**
>
> Create a Fibery account to replace isolated tools and bring everyone together.
In the report, I have graphed “Progress” over time. What is missing in the report is the upper bound – speaking in pseudo-code, the SUM(Task.[Time estimated]) as a horizontal line (“annotations”), meaning, the amount of time that should have been spent if all Task items had a progress of 100%. I cannot add this annotation to the existing line, because the field [Time estimated] is not available there. And I cannot add SUM(Task.[Time estimated]) as a new data row, because the Task entity has no date and thus nowhere for the value to be graphed on the timeline…
Best,
Lars
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [February 21, 2024, 4:22pm UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/4 "2024-02-21T16:22:57Z")
Based on your sample data, I was able to produce this chart:
Does it look close to what you need?
---
### Author:  [@lars](https://community.fibery.io/u/lars)
#### Post date: [February 22, 2024, 7:15am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/5 "2024-02-22T07:15:01Z")
Close, but not quite there yet 🙂
You’ve graphed the upper bound for every item separately. (You probably added a lookup to Task.Time estimated on the Progress database, right?)
What I need is the upper bound for the sum of all Tasks (!), which might be different from the sum of all Progress entities at 100% – in my example, Lorem and Ipsum have _no_ progress attached, yet should be counted in the total sum.
However, your approach led me to another idea: I could either add an auto-linking relation from progress to _every_ Task, and calculate the sum over this in a formula, or I could sum up all Task entities in an automation on the progress database. I will try this and report back.
Thanks so far for the idea!
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [February 22, 2024, 7:17am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/6 "2024-02-22T07:17:57Z")
So you wanted a single line to represent total progress over all tasks, and a horizontal line to represent the max value of this calculation?
In other words, no separation by task…?
---
### Author:  [@lars](https://community.fibery.io/u/lars)
#### Post date: [February 22, 2024, 7:56am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/7 "2024-02-22T07:56:38Z")
Not the actual MAX() value, but the theoretical max value. This theoretical maximum being: all existing tasks having a progress of 100% attached.
Starting from the automation idea, I’ve managed to have the graph display what I want. See the updated template for how I did it, and what I wanted to achieve. It’s a bit hacky (graph color = #FFFFFF, storing calculation results in a writable number field), but it works.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [February 22, 2024, 8:12am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/8 "2024-02-22T08:12:50Z")
> [@lars](#):
>
> Not the actual MAX() value, but the theoretical max value.
Sorry, that’s what I meant. The 100% value.
I have a suggestion for a solution which will avoid the need for an automation:
create a single-select field in the Task db, with a single option (= default for all Tasks) and then use a formula to calculate the theoretical max value.
See [here](https://shared.fibery.io/t/a7e4a0c9-8dde-496c-b7dc-a613aede27d3-lf-chart-annotation).
This select field should be hidden everywhere (so no-one de-selects the default option) but if you wanted, you could even make the single-select field read-only (via API) so that users can’t ever mess with it.
---
### Author:  [@lars](https://community.fibery.io/u/lars)
#### Post date: [February 22, 2024, 8:38am UTC](https://community.fibery.io/t/report-chart-annotation-for-values-not-graphed/5529/9 "2024-02-22T08:38:06Z")
Uuh, clever! For this usecase, I’ll probably leave it as is, but this is a handy trick to keep in mind for future stuff. Thanks!!