Unable to show JQL query due to auto appended DURING (X,Y) in JavaScript Charts for Jira Cloud

[Cynthia Lim]

Hi All, I've been trying to google for answers but am unable to find hence would hope if someone could advise please.

I'm looking to create a sprint Burndown Chart (using story points) filtered by both assignee and for subtasks only.

Using the filter function in JIRA to customise the JQL query (yes I'm not a developer) allows me to pull the right list of issues but when copied over to the JavaScript Charts for Jira Cloud gadget, it just ain't showing the right data.

Basically this was my JQL query, I've selected the 'None (sum of existing issues)' in the Time Series Field as per the tutorial and the intention for my story points to be sum up in the Burndown Chart.

project = TNG AND issuetype = Subtask AND status in ("In Progress", "To Do") AND assignee in (5ff28a3a44065f013f925bc) order by created DESC

Tried adding 'was' in the JQL query as per below advice but not working as well. https://community.atlassian.com/t5/Jira-discussions/JavaScript-Charts-for-JIRA-Cloud-Cumulative-chart/td-p/1260135

Also tried adding '$DURING' at the end of the JQL query as per below recommended solution but still ain't working. https://community.atlassian.com/t5/Jira-questions/Creating-a-custom-time-series-burndown-chart-using-JavaScript/qaq-p/1285090

Help please? If not, any recommendation for any other third party app integration to JIRA that allows me to filter by assignee and sub tasks would be greatly appreciated as well. Thanks!

[Nic Brough -Adaptavist-]

I'm afraid you'll need to look back at the process here.  There's a problem with what you're trying to do (which is partly why you're struggling to get to what you want)

You say (with my emphasis added):

"I'm looking to create a sprint Burndown Chart (using story points) filtered by both assignee and for subtasks only."

The problem here is that you do not burn down on subtasks.  Sub-tasks are part of their parent stories, they're not items you commit to doing individually.  Burn down happens when you complete a story, not a sub-task.  Jira simply doesn't have the data structure to support not doing scrum but using a burndown.