We are using Redash so that our Engineering department can visualize their project’s Jira metrics.

We have approx. 10 teams, with approx. 20 different Jira projects. Each project needs to have about 10 different graphs that each do something different, I.E. “Number of Tickets Per Dev Per Month”.

How It Works Now:
We have a Jira data source that has different queries per project. We tried having all projects in a single JQL query, but it takes like 30+ minutes and makes troubleshooting new queries impossible. We have tens of thousands of tickets going back years. So we made separate Jira queries per project.

We then use a Query Results data source, using “FROM query_xxxx” to perform SQL queries on that raw data from Jira. It works well! It does everything we want it to.

But we have a problem. This works well for one project and one dashboard. But we have 20 projects and 20 dashboards.

We tried using parameters to pass in the “query_xxx” part, so we can have one query per visualization for ALL the projects, but as soon as you change the param, the previous cached results are lost, and all of our other dashboards go blank. So that’s not a solution. All dashboards need to work all the time.

We considered forking the same query 20 times for every project, but that would be insane. We would have to manage 200+ queries, and any time one of them needs to be modified, we would have to update the other 20 queries that do the exact same thing but with a different query ID for each project.

Is there any way to use One “Query Results” Query, pass in the “query_xxx” ID from any “Jira” query, and be able to view the data without re-running all the queries again? Or something similar that would achieve the same thing? We don’t want to go back to doing all of this manually in an Excel spreadsheet :frowning:

You’re right that cloning is the only way to do this, for now.

From our documentation:

The QRDS doesn’t work with results from queries that use parameters. If you try it you’ll see Error running query: Failed loading results from query id xxxx . Remove the parameters from query_xxxx to fix the error.

Related discussion: