Release burndown chart - how does it pick up work items to associate them with the release?

[rona french]

We use fixversion on our epics but do not consistently use fix version on stories. Will the release burndown chart pick up stories that are linked to the epic using the Epic Link function where the epic has a fix version but the user story does not?

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @rona french ,

welcome to the Atlassian community!

Release Burdown is based on a fixVersion field so, if you have a story without a fixVersion, it will not appear on that report.

It's semantically correct because an epic could be associated to multiple release and, each story within that epic can have a specific release associated.

If you want to put in place that behaviour, you need to put in place an automation similar to this https://www.youtube.com/watch?v=Y5u_i9z06zg but editing fix version field.

Hope this helps,

Fabio

[rona french]

Thanks Fabio. That certainly helps me with a few ideas.

[Fabio Racobaldo _Herzum_]

you're welcome @rona french