How can I show number of open tickets at the end of each week in a graph on Jira Dashboard

[Marieke Cozijnsen]

I can retrieve the amount of tickets that were open at the end of each week using the JQL query of e.g.

Project = Y AND status was in ("Open", "In Progress") ON startOfWeek()

Project = Y AND status was in ("Open", "In Progress") ON startOfWeek(-1)

Project = Y AND status was in ("Open", "In Progress") ON startOfWeek(-2) etc.

Any way to show this in a graph on a Jira Dashboard? Or another way to do it instead of above formulas?

Preferably using a bar chart e.g:

[Michael Partyka]

Hi Morgan,

maybe you have condition in your workflow?

Upload your workflow here I will check it.

[MattS]

For humans, this is a good thing. It means that some colleague doesn't have to contact you three months later to ask why you closed it. For service accounts, it's a bit annoying but not too much. 

My money is on a Behaviour making this required

[Nic Brough -Adaptavist-]

When you say "would not close", what is the actual behaviour?  Is it churning when you click the commit?  Returning you to the issue view with nothing changed?  Error message?

[Morgan Thunder]

Hi Nic - I should have said - no error at all. Just nothing happens when you press the commit button. Then when you go back and add a comment, the button works and the issue closes.

[Nic Brough -Adaptavist-]

Hmm.  Do you have any custom javascript, or the Behaviours add-on installed (it's part of Script Runner now)?

[Morgan Thunder]

We do have Script Runner (and Behaviours) installed, yes.

[Nic Brough -Adaptavist-]

Ok, check the list of Behaviours that may be active - on a very old version (before it merged with SR I think), I remember managing to set up a behaviour that would do exactly what you're seeing - it was requiring a comment during transitions, but not telling the user why it wasn't letting them proceed (because I'd made a mess of the config)

[Morgan Thunder]

Thanks Nic, I'll check it out.