Deprecated: | In JIRA 4.0, portlets were replaced by gadgets. For details, please see Gadgets and JIRA Portlets. |
A portlet plugin module defines a portlet that users can add to their Dashboards.
The root element for the portlet plugin module is portlet
. It allows the following attributes and child elements for configuration:
Name | Required | Description | Default |
---|---|---|---|
class | yes | The class which implements this plugin module. The class you need to provide depends on the module type. For example, Confluence theme, layout and colour-scheme modules can use classes already provided in Confluence. So you can write a theme-plugin without any Java code. But for macro and listener modules you need to write your own implementing class and include it in your plugin. See the plugin framework guide to creating plugin module instances. The Java class of the component. Portlet implementation classes are required to implement the |
|
key | yes | The unique identifier of the plugin module. You refer to this key to use the resource from other contexts in your plugin, such as from the plugin Java code or JavaScript resources.
In the example, | N/A |
i18n-name-key |
| The localisation key for the human-readable name of the plugin module. |
|
name |
| The human-readable name of the plugin module. I.e. the human-readable name of the component. | The plugin key. |
Name | Required | Description |
---|---|---|
description |
| A human-readable description of this portlet module. May be specified as the value of this element for plain text or with the |
label | yes | The user-visible name of this portlet. May be specified as the value of this element for plain text or with the |
thumbnail |
| An optional thumbnail image used to preview the portlet for users. |
permission |
| Permission required to add this portlet to a dashboard. Value must be one of the fields of |
objectdescriptor |
| Allows configuration of this portlet with an object descriptor class (see this page for more details). We recommend using a |
lazy |
| Whether to load this portlet lazily. |
1 2<portlet key="assignedtome" name="Assigned Issues" class="com.atlassian.jira.portal.portlets.AssignedToMePortlet"> <description key="portlet.assignedtome.description">i18n description</description> <!-- this template produces the eventual HTML of the portlet --> <resource type="velocity" name="view" location="templates/plugins/jira/portlets/assignedtome.vm" /> <label key="portlet.assignedtome.name" /> <!-- an optional thumbmail image used to preview the portlet for users --> <thumbnail>portlets/dashboard/thumbnails/assigned.gif</thumbnail> <!-- the permissions required to add this portlet (optional - not often required) --> <permission>assignable</permission> <objectdescriptor key="portlet.assignedtome.display.name" /> <!-- same as the properties of the report plugin module --> <properties> <property> <key>numofentries</key> <name>portlet.assignedtome.field.numofentries.name</name> <description>portlet.assignedtome.field.numofentries.description</description> <type>long</type> <default>10</default> </property> </properties> </portlet>
Rate this page: