The point of gadgets is that they are the end point of a display. They're there to sit on the dashboard and look pretty in the direction of the users. They read data, work out a display for it, and draw that. That's what they're for. They are NOT designed for data exports or as intermediate points in a process, they are the end result.
If you want data that you see in a gadget in some other place, then you'll generally need to replicate the logic in whatever you are doing. Having said that, the logic is usually immensely simple, and often directly supported by the API. For example, if you want "data from the filter statistics gadget", then actually, all you need to do is read the statistics off the saved filter. Which is all the gadget is doing (before it gets onto the clever displays etc)
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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