Gadget release is the process of publishing a new version of a gadget to your Confluence site or Jira application. For example, you may wish to update a gadget to provide new features or fix bugs.
For example, you may want to create a new type of gadget that displays Jira data on a page or in the dashboard. For displaying simple Jira information, we recommend using macros instead of gadgets (such as the Jira Issues Macro or Jira Chart Macro) as these have better performance and are easier to configure.
Gadgets are the basic building blocks that make up your gadget backend. They can read or write records to your gadget database, and can also run server-side logic outside of the database. Actions are a core concept of Gadget and are a big part of why web app development with Gadget is faster and simpler than with other tools.
Interactions have key properties such as parameters and on_change, which configure how the script is loaded. For example, on iOS a path specifies where to look for the file in order to take advantage of iTunes file sharing or Apple’s AFC (which is only allowed for debuggable apps). The on_change option can be set to ignore or reload, enabling Gadget to monitor the file and reload it whenever it changes — this is recommended during development.
Other keys are a listen interaction and a teardown option, which specify what to do when the program is shut down. The default is minimal, which means we don’t shut down internal threads or free OS resources. The alternative is full, which will perform a more complete shutdown. Other options are the listen_port option, which specifies what TCP port to listen on for connections.