Jira modules allow add-ons to extend the functionality of the Jira platform or a Jira application. Jira modules are commonly used to extend the user interface by adding links, panels, etc. However, some Jira modules can also be used to extend other parts of Jira, like permissions and workflows. Jira Service Management and Jira Software also have their own application-specific modules (UI-related only).
You can use a Jira module by declaring it in your add-on descriptor, with the appropriate properties. For example, the following code uses a web section and web item to add a 'myItem' menu to the Jira header.
1 2<web-section name="mySection" i18n-name-key="my-section.name" key="my-section" location="my-item-link" weight="1000"> <description key="my-section.description">The mySection Plugin</description> </web-section> <web-item name="myItem" i18n-name-key="my-item.name" key="my-item" section="system.top.navigation.bar" weight="1000"> <description key="my-item.description">The myItem Plugin</description> <label key="my-item.label"></label> </web-item>
There are three kinds of basic module:
You can also insert custom web fragments into existing ones in Jira (e.g. web sections which are 'built in' to Jira). However, you cannot redefine Jira's existing web fragments. We recommend downloading the Jira source (valid Jira license required), so you can access the appropriate source files that define Jira's existing web fragments. This will help you:
key
values in your own <web-items>
and <web-sections>
remain unique.Basic modules can be used in the following locations in the Jira UI:
Advanced modules have pre-defined locations in Jira (e.g. Project tab panel module) or are used for a feature that is not related to the UI (e.g. Index document configuration module). These modules are also declared in your add-on descriptor, however you do not need to define a location for them.
In the list of modules below, any module which is not a basic module is an advanced module.
Rate this page: