# Burndown chart in vision

**URL:** <https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [February 12, 2025, 11:05am UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239 "2025-02-12T11:05:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Morten\_Jepsen](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Morten\_Jepsen](https://forum.inductiveautomation.com/u/Morten_Jepsen)\
**Post date:** [February 12, 2025, 11:05am UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239/1 "2025-02-12T11:05:31Z")

</div>

Im trying to make a burndown chart on ignition, but can find any suitable component. I make a workaround using a regular chart and a white stacked coloumn, but that have issues aswell. Box and whiskers might be a solution, but the median is bugging me. Anyone who found a good way og making one, similar to this

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0a2ea7e162323745178523a2b7a0587a0f4de298.png)

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 12, 2025, 12:23pm UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239/2 "2025-02-12T12:23:39Z")

</div>

Is it because the gridlines are hidden by the white bars? If so, you should be able to adjust the opacity of the color.

---

<div class="post-metadata">

**Author:** ![Morten\_Jepsen](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Morten\_Jepsen](https://forum.inductiveautomation.com/u/Morten_Jepsen)\
**Post date:** [February 12, 2025, 1:11pm UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239/3 "2025-02-12T13:11:47Z")

</div>

That helped on the looks, thx. I was just wondering if there were a more suitable solution that didnt require alot og math and tag binding to where the next bar should start/stop, but its doable with this.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 12, 2025, 1:37pm UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239/4 "2025-02-12T13:37:50Z")

</div>

If you can post a sample raw dataset and an end result dataset, I can probably help out with optimizing what you have.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 12, 2025, 1:40pm UTC](https://forum.inductiveautomation.com/t/burndown-chart-in-vision/102239/5 "2025-02-12T13:40:29Z")

</div>

Was also going to say that if this is coming from a database, we may be able to tweak the query to just give you the end result dataset. Let the db do the heavy lifting.