An SQL query is a pain - you would have to read every issue type screen scheme and screen scheme for the basic list of screens and where they are used, then the project configs to see which issue type screen schemes are in use where, and then read the whole workflow table parsing it for the screen ids in use in transitions, then the workflow schemes and the projects again.
The UI at leasts helps you a bit with this when you look at the list of screens.
That shows the projects associated with the issue type screen scheme but each screen could be associated with multiple issue type screen schemes. It gets pretty messy to roll up if you're doing widespread changes across many screens. I'm trying to determine scope for impact and communication purposes so I'm making an excel with the screen changed and the issue type screen scheme(s) associated, pasting all the associated projects then removing dupes but that "hidden projects" message would be so much more useful and less of a tease if it just revealed the rest of the projects so i could copy/pasta.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events