Technically, yes, it's all in tables, but it's not a direct relationship and some of the data is stored in blocks, not normalised in any way, so you can't just use SQL to get to it.
That brings me back to "why"? What are you trying to achieve here?
Right, well, that's "current usage" which is a statistic. The status that a project uses is not necessarily the same as what is currently in use.
It's also very easy to get to (unless you do it via the database, where it remains a bit of a pig, albeit a little easier than the original question)
Start a new filter, and blank it out. Save it with a name like "all issues". Go to your dashboard and add a filter statistics gadget, selecting "status" as the reporting variable and "all issues" for the filter. You now have a list of all status that are in use, and by how many issues.
It's not perfect, the gadget will drop lines where the total count is 0, but you can at least see the low usage ones, and you can use it to compare with the full list of status (if it's not on the gadget, then it's used by 0 issues and can be killed off. Or at least, check the workflow its using!)
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs