documentation for universal plugin manager...

Documentation for Universal Plugin Manager2.3

Documentation for Universal Plugin Manager 2.3 2

Created in 2012 by Atlassian. Licensed under a .Creative Commons Attribution 2.5 Australia License

Contents

Universal Plugin Manager Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Using the Universal Plugin Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Navigating to the Universal Plugin Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Viewing your Installed Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing a Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Configuring a Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Uninstalling a Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Viewing the Plugin Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Disabling or Enabling a Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Upgrading your Existing Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Checking Plugin Compatibility for Application Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Universal Plugin Manager FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Diagnosing base URL configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Problems Connecting to the Atlassian Plugin Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Upgrade tab shows java.net.ConnectException . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Contributing to the Universal Plugin Manager Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing the Universal Plugin Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Upgrading the Universal Plugin Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Universal Plugin Manager 2.3.X Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Universal Plugin Manager 2.2.X Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Universal Plugin Manager 2.1.X Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Universal Plugin Manager 2.0.X Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Universal Plugin Manager 1.6.X Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Universal Plugin Manager 1.5 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Universal Plugin Manager 1.4 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Universal Plugin Manager 1.3.2 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Universal Plugin Manager 1.3.0 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Universal Plugin Manager 1.2.4 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Universal Plugin Manager 1.2.3 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Universal Plugin Manager 1.2.2 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Universal Plugin Manager 1.2.1 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Universal Plugin Manager 1.2.0 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Universal Plugin Manager 1.1.4 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Universal Plugin Manager 1.1.3 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Universal Plugin Manager 1.1.2 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Universal Plugin Manager 1.1.1 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Universal Plugin Manager 1.1.0 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Universal Plugin Manager 1.0 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Universal Plugin Manager 1.0.2 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

http://creativecommons.org/licenses/by/2.5/au/



Universal Plugin Manager DocumentationThe Universal Plugin Manager (UPM) provides a set of functions for managing your plugins. The UPM is itself asystem plugin. It allows you to perform common tasks such as:

Enabling and disabling plugins and their plugin modules.Installing new plugins.Configuring advanced plugin options.Finding out-of-date plugins and updating them.Checking the compatibility of your installed plugins against newer versions of the application.

Through the UPM you can interact with the . You can use the UPM to browseAtlassian Plugin Exchangeavailable plugins for your application, and try or buy any of these plugins without ever leaving your application.

The Universal Plugin Manager (UPM) 2.3 is available for a number of Atlassian applications.Your application may contain an older version of the UPM. If you want the functionalitydescribed in this documentation, you should upgrade your UPM to 2.3. The plugin's page onthe Atlassian Marketplace lists .the latest compatible applications

Read more about the Universal Plugin Manager in the topics linked below:

Using the Universal Plugin ManagerUniversal Plugin Manager FAQContributing to the Universal Plugin Manager DocumentationInstalling the Universal Plugin ManagerUpgrading the Universal Plugin ManagerRelease Notes

Using the Universal Plugin Manager

Once you have , read the topics below for instructions on how to use it.installed the Universal Plugin Manager

Navigating to the Universal Plugin ManagerViewing your Installed PluginsInstalling a PluginConfiguring a PluginUninstalling a PluginViewing the Plugin Audit LogDisabling or Enabling a PluginUpgrading your Existing PluginsChecking Plugin Compatibility for Application Upgrades

Navigating to the Universal Plugin ManagerThe Universal Plugin Manager (UPM) is available in a number of Atlassian applications. Please see the relevantsection below for instructions on how to access the Universal Plugin Manager in your application.

On this page:

Accessing the Universal Plugin Manager in JIRAAccessing the Universal Plugin Manager in ConfluenceAccessing the Universal Plugin Manager in Bamboo

Accessing the Universal Plugin Manager in JIRA

Required Permissions: You need the to access the UniversalJIRA System Administrator global permissionPlugin Manager in JIRA.

http://creativecommons.org/licenses/by/2.5/au/http://plugins.atlassian.comhttps://plugins.atlassian.com/plugin/details/23915https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions



1. 2.

3.

1. 2.

To access the Universal Plugin Manager in JIRA:Log in as a user with the .JIRA Administrators global permissionSelect .AdministrationThe system displays the Administration page.Choose from the section. Plugins PluginsThe Universal Plugin Manager appears.

: start typing Keyboard shortcut g + g + plugins

Screenshot above: Universal Plugin Manager in JIRA

Accessing the Universal Plugin Manager in Confluence

Required Permissions: You need the Confluence to access theSystem Administrator global permissionUniversal Plugin Manager in Confluence.

To access the Universal Plugin Manager in Confluence:Choose > .Browse Confluence AdminClick the link in the section of the left-hand menu. The Universal Plugin ManagerPlugins Configurationwill appear.

Screenshot above: Universal Plugin Manager in Confluence

Accessing the Universal Plugin Manager in Bamboo

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/JIRA/Using+Keyboard+Shortcuts#UsingKeyboardShortcuts-administrationsearchdialogboxhttps://confluence.atlassian.com/display/DOC/Global+Permissions+Overview



1. 2. 3.

Required Permissions: You need the Bamboo to access the Universal Pluginglobal admin permissionManager in JIRA.

To access the Universal Plugin Manager in Bamboo:Log in as a user with the global permission.AdminClick the link in the top navigation bar.AdministrationIn the left-hand menu, under the title , click the link.System Plugins

Viewing your Installed PluginsYou can use the Universal Plugin Manager (UPM) to see the plugins installed on your application. These includeplugins that are bundled with your application as well as any plugins that you have installed. Both enabled anddisabled plugins are displayed.

On this page:

Viewing your installed pluginsViewing a plugin's detailsNotes

Viewing your installed plugins

To view your installed plugins:

Click the tab to list the plugins installed in your application. The application groups plugins intoManage Existing and . The are hidden by default. Use the followingUser-installed Plugins System Plugins System Plugins

actions when working with the plugin list:Enter keywords in the text box to filter the list.Filter visible pluginsClick the link to see the hidden system plugins.Show System PluginsClick the name of a plugin to view the plugins details.Click to run your application in safe mode. This mode disables all user installedEnable Safe Modeplugins.

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/BAMBOO/Granting+administration+rights+to+a+user



Screenshot above: Viewing Installed Plugins (Confluence)

Viewing a plugin's details

To see the details for a plugin, click the name of a plugin in the list of installed plugins. The summary contains ashort description of the plugin as well as buttons/links for plugin operations and related information.

Screenshot above: Viewing a Plugin's Details (Confluence)

Plugin key – A unique key that identifies each plugin in the system.Developer — The name of the plugin developer and a link to the developer's home page, if provided bythe plugin developer.Plugin version – The version of the plugin currently installed.Manage plugin modules — Click this link to display the plugin modules below the plugin summary. Amodule is a component of the plugin. This link will only appear if the plugin has modules. If you want toenable or disable a plugin module, hover your mouse over the module and click the ' '/' 'Enable Disablebutton for that module.Configure – Click this link to display the configuration settings for the plugin. This link is disabled if theplugin is disabled. Please note that not all plugins have settings that can be configured through the




Universal Plugin Manager.Disable – Click this button to disable the plugin in your application. This button will only appear if theplugin is enabled.Enable – Click this button to enable the plugin in your application. This button will only appear if theplugin is disabled.Uninstall – Click this button to uninstall the plugin from your application. This button will only appear foruser installed plugins.

NotesWhat is the difference between a 'system plugin' and a 'user installed plugin'?

System plugins are shipped with the application. These plugins are essential for the functioning ofthe system. Although you can disable some of them, you should not do so unless instructed by anAtlassian support engineer. Not every system plugin can be disabled. You cannot uninstallNote:any system plugins.User installed plugins are those which have been installed in the application after it was set up.You can install a plugin either by uploading a JAR file or via the Universal Plugin Manager. Youcan uninstall these plugins.

Related Topics

Configuring a PluginDisabling or Enabling a PluginUninstalling a Plugin

Installing a Plugin

The Universal Plugin Manager (UPM) provides you with a simple way of installing new plugins to yourapplication. Use plugins to customise and extend the functionality of your application. You can search for pluginsin the Universal Plugin Manager (sourced from the ) or upload your own.Atlassian Plugin Exchange

On this page:

Before you beginAdding a plugin from the Atlassian MarketplaceUploading your own plugin

Before you begin

Some things to note before you use the UPM:

In JIRA and Bamboo you cannot install or uninstall using the Universal Plugin Manager.version 1 pluginsVersion 1 JIRA plugins listed in the Universal Plugin Manager have a button, rather than an Download In

button. You must download the plugin distribution and follow its specific installation instructions.stallTypically, you download the plugin into the director/atlassian-jira/WEB-INF/liby as instructed in . Correspondingly, version 1 JIRA and Bamboo plugins do notManaging JIRA's Pluginshave an button. You must remove the plugin from the file system manually.UninstallIn Confluence, you can install and uninstall using the Universal Plugin Manager. Youversion 1 pluginsshould see an or an button with the plugin entry.Install Uninstall

Some entries that you find listed in the Universal Plugin Manager . For example, the are not actually plugins JIRA is a useful program that runs alongside JIRA, rather than inside it as a plugin. These entries have a Client Down

button that allows you to download the application to your desktop and run it following its specificloadinstructions.

Adding a plugin from the Atlassian Marketplace

View a demo of installing a plugin using the UPM:

http://creativecommons.org/licenses/by/2.5/au/https://plugins.atlassian.comhttps://confluence.atlassian.com/display/JIRA/Managing+JIRA%27s+Plugins#ManagingJIRA'sPlugins-installhttps://plugins.atlassian.com/plugin/details/7070https://plugins.atlassian.com/plugin/details/7070



1. 2.

3.

1.

2.

3.

4.

To find and add a plugin from the Atlassian Marketplace (formerly the Atlassian Plugin Exchange), navigate to and do the following:the pagePlugins

Click the tab in the UPM. You will see a list of featured plugins.InstallSearch for your plugin as follows:

Enter some keywords that describe the plugin in the search box andSearch the Plugin Exchangepress Enter.Alternatively, browse to the desired plugin in the list. You can choose , , Featured Popular Support

or from the dropdown to see a different list ofed (by Atlassian) All available Plugins to showplugins.

Click the button for the desired plugin to add it to your application. A confirmation message and theInstallplugin details will appear when the plugin is installed successfully.

You may need to restart your application for your change to take effect. The Universal PluginNote:Manager will inform you if this is the case.

Not all plugins can be automatically installed. Some required manual installation. These plugins willNote:have a button instead of an button. In these cases, you should read and follow theDownload Installplugin's installation instructions.

Screenshot above: Finding a new plugin from the Atlassian Plugin Exchange

Uploading your own plugin

To upload your own plugin, and do the following:navigate to the pagePlugins

Click the tab in the UPM. InstallThe system displays a list of featured plugins.Click the link. Upload PluginThe system displays the window.Upload PluginSpecify the location of your plugin:

If the plugin you want to install is on your computer, use the dialogue to choose the pluginBrowseJAR file.If you want to install a plugin from a remote location, enter the URL of the plugin JAR file in the Fro

text box.m this URLClick the button to upload and enable your plugin. A confirmation message will appear when theUploadplugin is successfully installed.

You may need to restart your application for your change to take effect. The Universal PluginNote:Manager will inform you if this is the case.




1. 2.

3.

4.

Screenshot above: Uploading a new plugin

Related Topics

Viewing your Installed Plugins#viewdetails

Configuring a Plugin

A number of plugins offer advanced configuration options. If you have one of these plugins installed on yourapplication instance, you can view and update these configuration options via the Universal Plugin Manager(UPM). (If you would like to disable or enable a plugin, please refer to .)Disabling or Enabling a Plugin

To configure a plugin via the UPM, and do the following:navigate to the pagePlugins

Click the tab.Manage my pluginsLocate the plugin that you want to configure and click its title. The plugin details section expands.Click the button for that plugin. The advanced configuration options appear.Configure

If the plugin is disabled, you cannot configure it, and therefore the button does notNote: Configureappear. If there are no advanced configuration options for the plugin, there is no button.Configure

Update the configuration settings as desired and save your changes. The plugin itself provides advanced configuration options. If you encounter any problems after youNote:

click the button, the plugin is responsible for the issue, not the UPM.Configure

Screenshot above: Configuring a plugin

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/UPM023/Viewing+your+Installed+Plugins#ViewingyourInstalledPlugins-viewdetailshttps://confluence.atlassian.com/display/UPM016/Disabling+or+Enabling+a+Plugin



1.

2.

3.

Screenshot above: Configuring a plugin — WebDAV configuration

Uninstalling a Plugin

You cannot uninstall plugins in JIRA 4.1 via the Universal Plugin Manager. See the Uninstalli section below for more information.ng Plugins in JIRA 4.1

If you wish to remove a plugin from your application altogether, you can uninstall it via the Universal PluginManager (UPM). If you only want to temporarily remove it, you may wish to instead.disable your plugin

To uninstall a plugin from your application and do the following:, navigate to the pagePlugins

Click the tab. Manage ExistingThe systems lists the plugins installed in your application.Click the name of the plugin that you wish to uninstall. The system displays the plugin details.Click the button. UninstallThe information summary displays an message and uninstalls the plugin from yourUninstallingapplication.

Screenshot above: Uninstalling a plugin




1.

2. 3.

1.

2. 3. 4.

Uninstalling plugins in JIRA 4.1

Due to a bug in the Atlassian Plugin Framework, the Universal Plugin Manager cannot uninstall plugins in JIRA. You can find more information about the bug here:4.1.x

https://studio.atlassian.com/browse/UPM-595https://studio.atlassian.com/browse/PLUG-598

If you need to uninstall a plugin, please follow the .JIRA 4.1 documentation for uninstalling a plugin

This bug has already been fixed in , which will be present in JIRA 4.2 and later.Atlassian Plugin Framework 2.5A newer version of the Universal Plugin Manager will reinstate the ability to uninstall plugins in JIRA.

Viewing the Plugin Audit Log

The Universal Plugin Manager (UPM) keeps a log of all plugin activity in the UPM, such as adding plugins,enabling plugins, and so on. You can configure the audit log to adjust the period of time for which log entriesshould be kept.

Viewing the plugin audit log

To view the plugin audit log, and do the following:navigate to the pagePlugins

Click the tab. Audit LogThe plugin audit log appears with a list of the 25 most recent entries.Use the arrows if you want to view older entries.Click the orange RSS icon if you want to receive the audit log activity in an RSS feed.

Screenshot above: Viewing the plugin audit log

Configuring the plugin audit log

To configure the amount of time log entries are kept, and do the following:navigate to the pagePlugins

Click the tab. Audit LogThe plugin audit log appears.Click the link.Configure purge policySpecify how many days to keep the logs before purging in the field.Purge audit log afterClick the button.Confirm

http://creativecommons.org/licenses/by/2.5/au/https://studio.atlassian.com/browse/UPM-595https://studio.atlassian.com/browse/PLUG-598https://confluence.atlassian.com/display/JIRA041/Managing+JIRA%27s+Plugins#ManagingJIRA'sPlugins-UninstallingaJIRAPlugin



1. 2. 3. 4.

1. 2. 3. 4.

Screenshot above: Configuring the audit log's purge policy

Disabling or Enabling a PluginThe allows you to disable a plugin in your application instance withoutUniversal Plugin Manager (UPM)permanently removing it. If you want to remove a plugin from your application instance altogether, please refer to

.Uninstalling a Plugin

You can also disable all user installed plugins in your application, by enabling Safe Mode. This may help you todiagnose a plugin-related problem more easily.

On this page:

Disabling a pluginEnabling a pluginDisabling/enabling all user installed plugins (safe mode)

Disabling a plugin

To disable a plugin in your application, and do the following:navigate to the pagePlugins

Click the tab. You will see a list of the plugins installed in your application.Manage my pluginsLocate the plugin that you want to disable and click the title to expand the plugin details section.Click the button.DisableOnce a plugin has been disabled, you need to restart your application for your change to take effect.mayIf so, you will see a message for the plugin.Once the plugin is fully disabled, you will see an link for the plugin.Enable

Screenshot above: Disabling a plugin

Enabling a plugin

To enable a plugin in your application, and do the following:navigate to the pagePlugins

Click the tab. You will see a list of the plugins installed in your application.Manage ExistingLocate the plugin that you want to enable and click the title to expand the plugin details section.Click the button.EnableOnce a plugin has been enabled, you need to restart your application for your change to take effect.may




4.

1.

2. 3.

4.

5.

If so, you will see a message for the plugin: 'Enabled, requires restart'.Once the plugin is fully disabled, you will see a link for the plugin.Disable

Screenshot above: Enabling a plugin

Disabling/enabling all user installed plugins (safe mode)

Running your application in 'safe mode' disables all user installed plugins at once. All plugins that were disabledwhen you entered Safe Mode will be re-enabled when you exit Safe Mode. To enable safe mode, navigate to the

and do the following: pagePlugins

Click the tab. Manage my pluginsThe system displays a list the installed plugins.Click the link.Enable Safe ModeClick the button in the confirmation window. ContinueAll user installed plugins will be disabled and your application will now be running in safe mode.Make changes to your installed plugins as desired. For example, you may want to enable/disable specific plugins or plugin modules.Exit safe mode by clicking one of the links in the Safe Mode banner:

Click to restore your pluginExit Safe Mode and restore the previous configurationconfiguration to its state before you entered Safe Mode.Click to keep all changes made to yourExit Safe Mode and keep the current configurationplugin configuration during Safe Mode.

Screenshot above: Running Confluence in safe mode

Upgrading your Existing PluginsPlugins are often developed separately from your application. You may wish to upgrade your plugins to morerecent versions to allow them to work with your application version or simply to take advantage of new featuresin a plugin version. The Universal Plugin Manager (UPM) provides you with a list of plugins that have availableupgrades and allows you to upgrade each plugin individually or in bulk.




1.

2. 3.

1.

2.

On this page:

Upgrading a pluginUpgrading all pluginsNotes

Upgrading a plugin

To upgrade a plugin, and do the following:navigate to the pagePlugins

Click the tab. You will see a list of plugins that are available for upgrading, under theManage my pluginsheading 'Available Updates'.

If there is a later version of a plugin that you have already installed, this page will show the latest c version of the plugin.ompatible

You can click the plugin name to expand the row and see more information about the plugin.You can filter your list by entering keywords in the text box.Filter visible plugins

Click the name of the plugin that you want to upgrade, to see more information about the plugin.Click the button next to the plugin to update it to the version shown.Update

Upgrading all plugins

To upgrade all available plugins, and do the following:navigate to the pagePlugins

Click the tab. You will see a list of plugins that are available for upgrading, under theManage my pluginsheading 'Available Updates'.

If there is a later version of a plugin that you have already installed, this page will show the latest c version of the plugin.ompatible

You can click the plugin name to expand the row and see more information about the plugin.You can filter your list by entering keywords in the text box.Filter visible plugins

Click the button to upgrade every plugin to the plugin versions shown.Update All

Note: Not all plugins can be installed or upgraded via the Universal Plugin Manager. There are someplugins that you must manually install and upgrade.




1. 2.

3. 4.

Screenshot above: Upgrading Plugins

Notes

Checking plugin compatibility for application upgrades. If you are considering upgrading your application,you can use the Universal Plugin Manager to check the compatibility of your plugins with your desiredapplication version. See .Checking Plugin Compatibility for Application Upgrades

Checking Plugin Compatibility for Application Upgrades

The in the Universal Plugin Manager (UPM) helps you to check whether yourApplication Upgrade Checkplugins will still work with your application after an application upgrade.

For example, if you were thinking of upgrading from Confluence 3.1 to Confluence 3.2, the Application UpgradeCheck can tell you the following:

Installed plugins that are compatible with Confluence 3.1 and Confluence 3.2Installed plugins that are not compatible with Confluence 3.2, but will be compatible with Confluence 3.2 ifyou upgrade them.Installed plugins that are not compatible with Confluence 3.2, even if you upgrade them to the latestversion.

To check compatibility of your plugins against different application versions, andnavigate to the pagePluginsdo the following:

Click the tab.Upgrade CheckIn the dropdown menu, select the version of your application to check theCheck compatibility forplugins against.Click the button.CheckThe page display any of your installed plugins that are not compatible with the selected applicationversion. The compatibility checker will also check the compatibility of the latest available version of each




4.

plugin (if not already upgraded). You can click on the name of any of the plugins to view more informationabout the plugin.

The plugins are grouped into sections under the following headings:Incompatible – The installed versions of these plugins are not compatible with the selectedapplication version. There are currently no plugin upgrades available that are compatible with theselected application version.Compatible, if upgraded – The installed versions of these plugins are not compatible with theselected application version. However, the plugins will be compatible if you upgrade them. Thereare buttons allowing you to upgrade these plugins.Compatible if both and the plugin are upgraded – The installed versions ofthese plugins are not compatible with the selected application version. There is a plugin compatiblewith the newer application version, but it is not compatible with the application version you arecurrently running. You must upgrade the application and upgrade the plugin. There arethenbuttons allowing you to disable these plugins before proceeding with the upgrade.Compatible – The currently installed versions of these plugins are compatible with the selectedapplication version.Unknown – These plugins may or may not be compatible with the selected application version. If aplugin is not registered with the , the Universal Plugin Manager cannotAtlassian Plugin Exchangecheck its compatibility with different application versions.

Screenshot above: Checking plugin compatibility against different Confluence versions

Universal Plugin Manager FAQ

http://creativecommons.org/licenses/by/2.5/au/https://plugins.atlassian.com



Universal Plugin Manager FAQ

Answers to commonly raised questions about configuring and using Universal Plugin Manager:

Diagnosing base URL configuration problemsProblems Connecting to the Atlassian Plugin ExchangeUpgrade tab shows java.net.ConnectException

Need more help?

Do you have a question, or need help with the Universal Plugin Manager? Please create asupport request

Diagnosing base URL configuration problems

Most of the content displayed on the UPM page is loaded dynamically via AJAX requests. Most of the requeststo the system use relative URLs, which will function correctly whether or not your instance's base URL isconfigured properly. However, by design, some long running operations (for example, plugin installation andupgrade) make requests using absolute URLs. If your instance's base URL is not configured properly, the UPMwill display a warning informing you that the base URL of your instance may be misconfigured.

The UPM depends not only on the Base URL, but also on the web browser URL so that the Javascript files canbe loaded. So please make sure that matthe URL being used to access the application in the web browserches the one provided at the .Base URL configuration

This does not indicate that there was a problem performing the operation itself. It simply indicates that the UPMcouldn't display the progress of the operation. If you refresh the UPM page, you should see the result of theoperation in the audit log.

In order to fix the problem, you may need to update the base URL settings in your instance. See the followingproduct documentation pages for instructions:

JIRAConfluenceBambooFisheyeStash

UPM depends not only on the Base URL, but also on the Browser URL so that the Javascript files can beloaded.

the URL being used to access the application in the web browser must match the one provided at the BaseURL configuration".

Problems Connecting to the Atlassian Plugin Exchange

The Universal Plugin Manager (UPM) needs to connect to the on the Internet in orderAtlassian Plugin Exchangeto:

Search for new plugins to install.Install new plugins from an Internet location.Find information about upgradable plugins.Perform an upgrade check.Upgrade plugins.

Specifically, your application must be able to contact . The UPM will useserver https://marketplace.atlassian.com

http://creativecommons.org/licenses/by/2.5/au/https://support.atlassian.com/secure/Dashboard.jspahttps://support.atlassian.com/secure/Dashboard.jspahttp://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Optionshttp://confluence.atlassian.com/display/DOC/Configuring+the+Server+Base+URLhttps://confluence.atlassian.com/display/BAMBOO/Specifying+Bamboo%27s+URLhttps://confluence.atlassian.com/display/FISHEYE/Configuring+the+FishEye+Web+Serverhttps://confluence.atlassian.com/display/STASH/Specifying+the+base+URL+for+Stashhttp://plugins.atlassian.comhttps://marketplace.atlassian.com/



the proxy settings of the host application. See the / .Confluence documentation JIRA Documentation

If you see an error message telling you that the UPM cannot reach the Internet, you should ask your networkadministrator whether your application server can make a request to that URL. If not, you must disable theconnection to Atlassian Plugin Exchange as explained in the following paragraph.

Using the UPM without an Internet Connection

If you wish to use the UPM without an Internet connection:

You should disable the connection to the Atlassian Plugin Exchange. This feature is available in UPM 1.5.and later

Set the system property to . When this property is set to true, then UPMupm.pac.disable truewill not try to access the Atlassian Plugin Exchange. Example:

-Dupm.pac.disable=true

Refer to the application documentation to see how to set a system property: , , Bamboo Confluence, .FishEye/Crucible JIRA

If going through a proxy, set up your proxy such that calls from your application (Confluence, JIRA, etc) toitself are not routed through the proxy.Do not use your browser's 'work offline' mode. The UPM will not work if this feature is enabled.

The following features will work without an Internet connection:

Managing existing plugins.Uploading plugin a plugin JAR from a local server.Audit logging.

NotesIf you are using the UPM without an Internet connection, the ' ' tab will inform you that Upgrade your

. It will not list any plugins available for upgrade, even if there are new versionsapplication is up to dateof your plugins available on the Atlassian Plugin Exchange.If you have the Numbered Heading plugin installed, you may encounter this known issue: Universal

.Plugin Manager Crashes when Numbered Headings Plugin is InstalledApril 2011: The development team have released a new version of the UPM plugin, which fixes someproblems associated with proxies. You can download the plugin here:https://marketplace.atlassian.com/pl

. For details, and to report any furtherugins/com.atlassian.upm.atlassian-universal-plugin-manager-pluginproblems or other comments, please refer to this issue: .UPM-1100

Upgrade tab shows java.net.ConnectException

If you see an error box on the upgrade tab containing the message java.net.ConnectException:, your host application server may be having trouble contacting Connection refused: connect http://plugin

. This may be a problem with your application's proxy settings.s.atlassian.com

Note: the Universal Plugin Manager will access and use the proxy settings of the host application. Seedocumentation for :

JIRAConfluence

as well as UPM-693

Contributing to the Universal Plugin Manager Documentation

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/DOC/Configuring+Web+Proxy+Support+for+Confluencehttps://confluence.atlassian.com/display/JIRAKB/Configure+Web+Proxy+Support+for+JIRAhttps://confluence.atlassian.com/display/BAMBOO/Configuring+system+propertieshttps://confluence.atlassian.com/display/DOC/Configuring+System+Propertieshttps://confluence.atlassian.com/display/FISHEYE/Setting+JVM+System+Propertieshttps://confluence.atlassian.com/display/JIRA/Setting+Properties+and+Options+on+Startuphttps://confluence.atlassian.com/display/CONFKB/Universal+Plugin+Manager+Crashes+when+Numbered+Headings+Plugin+is+Installedhttps://confluence.atlassian.com/display/CONFKB/Universal+Plugin+Manager+Crashes+when+Numbered+Headings+Plugin+is+Installedhttps://marketplace.atlassian.com/plugins/com.atlassian.upm.atlassian-universal-plugin-manager-pluginhttps://marketplace.atlassian.com/plugins/com.atlassian.upm.atlassian-universal-plugin-manager-pluginhttps://studio.atlassian.com/browse/UPM-1100http://plugins.atlassian.comhttp://plugins.atlassian.comhttp://confluence.atlassian.com/display/JIRA/Configuring+Apache+Reverse+Proxy+Using+the+AJP+Protocolhttp://confluence.atlassian.com/display/DOC/Configure+Web+Proxy+Support+for+Confluencehttps://studio.atlassian.com/browse/UPM-693



Would you like to share your hints, tips and techniques for the Universal Plugin Manager? We welcome yourcontributions. Have you found a mistake in the documentation, or do you have a small addition that would be soeasy to add yourself rather than asking us to do it? You can update the documentation page directly.

Getting permission to update the documentation

Our documentation wiki contains developer-focused documentation (such as API guides, plugin and gadgetdevelopment guides and guides to other frameworks) as well as product documentation (user's guides,administrator's guides and installation guides). The wiki permissions are different for each type ofdocumentation.

If you want to update the or other developer-focused wiki spaces, just sign up for aDeveloper Networkwiki username then log in and make the change.If you want to update the , we ask you to sign theUniversal Plugin Manager product documentationAtlassian Contributor License Agreement (ACLA) before we grant you wiki permissions to update thedocumentation space. Please read the to see the terms of the agreement and the documentation itACLAcovers. Then sign and submit the agreement as described on the form attached to that page.

Following our style guide

Please read our short .guidelines for authors

How we manage community updates

Here is a quick guide to how we manage community contributions to our documentation and the copyright thatapplies to the documentation:

Monitoring by technical writers. The Atlassian technical writers monitor the updates to thedocumentation spaces, using RSS feeds and watching the spaces. If someone makes an update thatneeds some attention from us, we will make the necessary changes.Wiki permissions. We use wiki permissions to determine who can edit the documentation spaces. Weask people to sign the (ACLA) and submit it to us. That allowsAtlassian Contributor License Agreementus to verify that the applicant is a real person. Then we give them permission to update thedocumentation.Copyright. The Atlassian documentation is published under a Creative Commons CC BY license.Specifically, we use a . This means that anyone canCreative Commons Attribution 2.5 Australia Licensecopy, distribute and adapt our documentation provided they acknowledge the source of thedocumentation. The CC BY license is shown in the footer of every page, so that anyone who contributesto our documentation knows that their contribution falls under the same copyright.

RELATED TOPICS

Contributing to the JIRA DocumentationContributing to the Confluence DocumentationAuthor GuidelinesAtlassian Contributor License Agreement

Installing the Universal Plugin Manager

The Universal Plugin Manager (UPM) 2.3 is available for a number of Atlassian applications. Your applicationmay contain an older version of the UPM. If you want the functionality described in this documentation, youshould upgrade your UPM to 2.3. The plugin's page on the Atlassian Marketplace lists the latest compatible

.applications

Installing the UPM into Confluence or JIRA for the first time

In most cases, you will not need to install the UPM, because it is bundled with the application. Please refer to the for instructions on replacing an existing version of the UPM. Follow the instructions below if youupgrade guide

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/UPMhttps://confluence.atlassian.com/display/ALLDOC/Atlassian+Contributor+License+Agreementhttps://confluence.atlassian.com/display/ALLDOC/Author+Guidelineshttps://confluence.atlassian.com/display/ALLDOC/Atlassian+Contributor+License+Agreementhttp://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/JIRA/Contributing+to+the+JIRA+Documentationhttps://confluence.atlassian.com/display/DOC/Contributing+to+the+Confluence+Documentationhttps://confluence.atlassian.com/display/ALLDOC/Author+Guidelineshttps://confluence.atlassian.com/display/ALLDOC/Atlassian+Contributor+License+Agreementhttps://plugins.atlassian.com/plugin/details/23915https://plugins.atlassian.com/plugin/details/23915



1. 2.

3.

do need to install the Universal Plugin Manager into a Confluence or JIRA site that does not yet have it.

Download the Universal Plugin Manager plugin from the .Atlassian Plugin ExchangeInstall the Universal Plugin Manager plugin in your application. The relevant instructions for installingplugins in each of the applications is available below:

The UPM is included by default in and later. If you are using an older version of JIRA,JIRA 4.3please refer to the . Note: The Universal Plugin Manager plugin is a 'Version 2'JIRA documentation(OSGi) plugin.The UPM is included by default in and later. If you are using an older version ofConfluence 3.4Confluence, please refer to the .Confluence documentation

The Universal Plugin Manager will be enabled by default. You will now be able to access the UniversalPlugin Manager by following the instructions on .Navigating to the Universal Plugin Manager

Screenshot above: Universal Plugin Manager installed in Confluence

RELATED TOPICS

Upgrading the Universal Plugin Manager

Upgrading the Universal Plugin Manager

This page tells you how to upgrade the Universal Plugin Manager (UPM). It contains the following topics:

BackgroundUpgrading the UPM (from version 1.6 or higher)Upgrading the UPM (from version 1.5 or lower)Alternative ways of upgrading the UPMTroubleshooting

Background

http://creativecommons.org/licenses/by/2.5/au/https://plugins.atlassian.com/plugin/details/23915https://confluence.atlassian.com/display/JIRA/JIRA+4.3+Release+Noteshttps://confluence.atlassian.com/display/JIRA/Managing+JIRA%27s+Pluginshttps://confluence.atlassian.com/display/DOC/Confluence+3.4+Release+Noteshttps://confluence.atlassian.com/display/DOC/Installing+a+Plugin



1. 2.

3.

4.

1.

2. 3. 4.

5. 6. 7. 8. 9.

1. 2.

3.

The UPM is itself a plugin. Of course, the tool used to install and manage plugins is the UPM itself.

Upgrading the UPM (from version 1.6 or higher)

Starting with version 1.6, UPM supports a simpler procedure for upgrading itself. Note that this will only work ifthe currently installed version is at least 1.6; if you are upgrading from 1.5 1.6, you must use the old proceduretodescribed above.

To upgrade the UPM:

Log in to your application as a system administrator.Go to the section on your application's administration screen. This is the plugins Universal Plugin

.ManagerIf a new version of UPM is available from the Atlassian Plugin Exchange, you will see this banner:

Click the "click here" link. UPM downloads and installs the new version in one step. You do not need torestart the application.

Upgrading the UPM (from version 1.5 or lower)

To upgrade the UPM, you need to install a new version of the UPM JAR file. Follow the steps below to upgradethe Universal Plugin Manager in JIRA, Confluence, FishEye or Crucible, if the currently installed version is 1.5 orlower.

To upgrade the UPM:

Download the latest version of the UPM plugin from the Atlassian Marketplace (formerly the Plugin.Exchange)

Log in to your Atlassian application as a user with permissions.administratorClick from the dashboard.AdministrationGo to the section. PluginsThis is the UPM.Navigate to the tab.InstallClick .Upload PluginBrowse to the UPM plugin JAR that you downloaded in step 1 and select it.Press .UploadRestart the application.You may need to restart twice.

If you are upgrading the UPM in Confluence 3.4.x, restart Confluence a second time.(See bug report . Note that this bug affects Confluence versions in theCONF-223233.4.x line only.)

Alternative ways of upgrading the UPM

If for some reason you cannot use one of the upgrade methods described above, you can use the followingmethods instead.

Fallback method for upgrading the UPM in JIRA:

Download the latest version of the UPM plugin from the .Atlassian Plugin ExchangeCopy the plugin JAR file into your JIRA home directory:\plugins\installed-plugins

Restart JIRA.

http://creativecommons.org/licenses/by/2.5/au/https://plugins.atlassian.com/plugins/com.atlassian.upm.atlassian-universal-plugin-manager-pluginhttps://plugins.atlassian.com/plugins/com.atlassian.upm.atlassian-universal-plugin-manager-pluginhttp://jira.atlassian.com/browse/CONF-22323https://plugins.atlassian.com/plugin/details/23915



1. 2.

3.

4.

1. 2. 3. 4.

5. 6. 7.

8.

1. 2.

3. 4. 5.

Fallback method for upgrading the UPM in Confluence:

Download the latest version of the UPM plugin from the .Atlassian Plugin ExchangeGo to this URL on your Confluence site:

http:///admin/viewplugins.action

The earlier version of the Confluence appears. Click , find the UPM plugin JARPlugin Manager Browsethat you downloaded in step 1, and upload the JAR into Confluence.Restart Confluence.

Fallback method for upgrading the UPM in FishEye:

Download the latest version of the UPM plugin from the .Atlassian Plugin ExchangeShutdown your FishEye instance;Open the ;$FISHEYE_INST/plugins/bundled-plugins.zipDelete (not extract) the existing froatlassian-universal-plugin-manager-plugin-x.x.x.jarm the zip file;Drag and drop the new plugin version from the folder it was downloaded to into the zip file;Close the zip file;Delete the $FISHEYE_INST/var/plugins/bundled/atlassian-universal-plugin-manager-

file;plugin-x.x.x.jarStart your instance again.

Troubleshooting

Upgrading the UPM without internet access – installation seems to fail

You can upgrade the UPM to version 1.5 to allow it to work better when there is no connection to the AtlassianPlugin Exchange (for example, because you have no Internet connection). Due to a bug in older versions ofUPM, the installation will appear to fail when there is no connection to the Atlassian Plugin Exchange, but theinstallation should still actually work.

To upgrade your UPM plugin where you have no Internet connection:

Obtain the UPM JAR from the .Atlassian Plugin ExchangeFollow .the instructions to upload the pluginDepending on your UPM version, this could appear to fail in various ways, such as just returningimmediately, or keeping an installation dialog up forever. In such cases, the installation is not actuallyfailing but just looks that way due to problems with older UPM versions.Wait a few minutes for the installation to finish in the background, then do a hard refresh of the page.Go to the tab.Manage ExistingYou should see version 1.5 under .Atlassian Universal Plugin Manager Plugin User-installed Plugins

After you have successfully installed UPM 1.5 or later, future plugin installations should no longer appear to fail.

More troubleshooting

Please refer to the following sources of information:

Confluence Knowledge BaseJIRA Knowledge BaseUPM issue tracker

Release Notes

http://creativecommons.org/licenses/by/2.5/au/https://plugins.atlassian.com/plugin/details/23915https://plugins.atlassian.com/plugin/details/23915https://plugins.atlassian.com/plugin/details/23915?versionId=335281http://confluence.atlassian.com/display/UPM/Adding+a+Plugin#AddingaPlugin-Uploadingyourownpluginhttps://confluence.atlassian.com/display/CONFKB/Universal+Plugin+Manager+%28UPM%29+Troubleshootinghttps://confluence.atlassian.com/display/JIRAKB/Plugins+Troubleshootinghttps://studio.atlassian.com/browse/UPM



The following pages list the JIRA issues resolved for the UPM releases:

Universal Plugin Manager 2.7.X Release NotesUniversal Plugin Manager 2.6.X Release NotesUniversal Plugin Manager 2.5.X Release NotesUniversal Plugin Manager 2.4.X Release NotesUniversal Plugin Manager 2.3.X Release NotesUniversal Plugin Manager 2.2.X Release NotesUniversal Plugin Manager 2.1.X Release NotesUniversal Plugin Manager 2.0.X Release NotesUniversal Plugin Manager 1.6.X Release NotesUniversal Plugin Manager 1.5 Release NotesUniversal Plugin Manager 1.3.0 Release NotesUniversal Plugin Manager 1.1.1 Release NotesUniversal Plugin Manager 1.1.0 Release NotesUniversal Plugin Manager 1.1.4 Release NotesUniversal Plugin Manager 1.2.4 Release NotesUniversal Plugin Manager 1.3.2 Release NotesUniversal Plugin Manager 1.2.2 Release NotesUniversal Plugin Manager 1.1.2 Release NotesUniversal Plugin Manager 1.4 Release NotesUniversal Plugin Manager 1.2.3 Release NotesUniversal Plugin Manager 1.1.3 Release NotesUniversal Plugin Manager 1.0.2 Release NotesUniversal Plugin Manager 1.0 Release NotesUniversal Plugin Manager 1.2.1 Release NotesUniversal Plugin Manager 1.2.0 Release Notes

Universal Plugin Manager 2.3.X Release Notes

The following table lists the JIRA issues resolved for the 2.3.X release.

(74 issues)JIRA Issues

Type Key Summary Priority Status Resolution

UPM-2435 UPM pluginassumes alicense ispresent,unfortunatelogging on freshFECRU install

Resolved Fixed

UPM-2138 Progress barnever moveswhenself-updating

Resolved Fixed

UPM-2136 Self updatebroken

Resolved Fixed

UPM-2131 "Show pricingdetails" link doesnothing

Resolved Fixed

UPM-2126 "InstalledVersion" missinga colon afterproperty tag

Resolved Fixed

UPM-2123 Don't wrap Fixed

http://creativecommons.org/licenses/by/2.5/au/https://confluence.atlassian.com/display/UPM023/Universal+Plugin+Manager+2.7.X+Release+Noteshttps://confluence.atlassian.com/display/UPM023/Universal+Plugin+Manager+2.6.X+Release+Noteshttps://confluence.atlassian.com/display/UPM023/Universal+Plugin+Manager+2.5.X+Release+Noteshttps://confluence.atlassian.com/display/UPM023/Universal+Plugin+Manager+2.4.X+Release+Noteshttps://ecosystem.atlassian.net/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20UPM%20AND%20fixVersion%20in%20%2816989,%2016361%29%20AND%20status%20in%20%28Resolved,%20Closed%29&tempMax=1000https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2435https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2138https://ecosystem.atlassian.net/browse/UPM-2136https://ecosystem.atlassian.net/browse/UPM-2136https://ecosystem.atlassian.net/browse/UPM-2136https://ecosystem.atlassian.net/browse/UPM-2136https://ecosystem.atlassian.net/browse/UPM-2131https://ecosystem.atlassian.net/browse/UPM-2131https://ecosystem.atlassian.net/browse/UPM-2131https://ecosystem.atlassian.net/browse/UPM-2131https://ecosystem.atlassian.net/browse/UPM-2131https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2126https://ecosystem.atlassian.net/browse/UPM-2123https://ecosystem.atlassian.net/browse/UPM-2123



plugin names ifthere's still a lotof space

Resolved

UPM-2122 Module list inplugin detailscan't beexpanded

Resolved Fixed

UPM-2121 Plugin details onUpdate Checkpage have lots ofwhite space

Resolved Fixed

UPM-2119 Empty bulletpoint when itshould have thePlugin SystemsVersion there

Resolved Fixed

UPM-2116 Version detailson Find NewPlugins needmore padding

Resolved Fixed

UPM-2103 Install pageconsistentlytimes out hittingproduction PAC

Resolved Fixed

UPM-2098 Add method toplugin licensestorage lib todeterminewhether or notenvironment isOnDemand

Resolved Fixed

UPM-2097 UPM logo doesnot havetransparency

Resolved Fixed

UPM-2094 Update all PACurl references tobemarketplace.atlassian.com

Resolved Fixed

UPM-2091 Make sure pluginis expandedbefore trying toshow inline errormessages.

Resolved Fixed

UPM-2082 Clicking"Uninstall" bringsyou to the top ofthe page

Resolved Fixed

UPM-2080 "You may closethis window."

Resolved Fixed

UPM-2079 Improvements tothe Success!

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-2123https://ecosystem.atlassian.net/browse/UPM-2123https://ecosystem.atlassian.net/browse/UPM-2123https://ecosystem.atlassian.net/browse/UPM-2123https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2122https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2121https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2119https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2116https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2103https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2098https://ecosystem.atlassian.net/browse/UPM-2097https://ecosystem.atlassian.net/browse/UPM-2097https://ecosystem.atlassian.net/browse/UPM-2097https://ecosystem.atlassian.net/browse/UPM-2097https://ecosystem.atlassian.net/browse/UPM-2097https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2094https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2091https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2082https://ecosystem.atlassian.net/browse/UPM-2080https://ecosystem.atlassian.net/browse/UPM-2080https://ecosystem.atlassian.net/browse/UPM-2080https://ecosystem.atlassian.net/browse/UPM-2080https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2079



modal afterinstalling aplugin

UPM-2078 Modal dialog foradd-on withlicense detectedneeds title

Resolved Fixed

UPM-2074 Whenenable/disablebuttons errorsout, and you'reway down thescreen, you can'tsee the errormessage above

Resolved Duplicate

UPM-2073 Back-end errorduring UpdateAll

Resolved Fixed

UPM-2069 Manage Plugins:MarketplaceListing link doesnot open in newwindow/tab

Resolved Duplicate

UPM-2066 MarketplacePaid plugins onFind NewPlugins tab don'tshow any prices

Resolved Invalid

UPM-2063 Crucible pluginscannot beupdated

Resolved Fixed

UPM-2060 Documentation& Support linksare broken inplugin details onManage page

Resolved Fixed

UPM-2057 Plugin key getsword-wrappedand thencropped

Resolved Duplicate

UPM-2055 The Paidterminology nearthe pricingmakes it look likeI have alreadypaid for a plugin

Resolved Fixed

UPM-2053 Buy / Try buttonsshould bestacked vertically

Resolved Fixed

UPM-2050 Change "FullAtlassianMarketplace" to

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2079https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2078https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2074https://ecosystem.atlassian.net/browse/UPM-2073https://ecosystem.atlassian.net/browse/UPM-2073https://ecosystem.atlassian.net/browse/UPM-2073https://ecosystem.atlassian.net/browse/UPM-2073https://ecosystem.atlassian.net/browse/UPM-2073https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2069https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2066https://ecosystem.atlassian.net/browse/UPM-2063https://ecosystem.atlassian.net/browse/UPM-2063https://ecosystem.atlassian.net/browse/UPM-2063https://ecosystem.atlassian.net/browse/UPM-2063https://ecosystem.atlassian.net/browse/UPM-2063https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2060https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2057https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2055https://ecosystem.atlassian.net/browse/UPM-2053https://ecosystem.atlassian.net/browse/UPM-2053https://ecosystem.atlassian.net/browse/UPM-2053https://ecosystem.atlassian.net/browse/UPM-2053https://ecosystem.atlassian.net/browse/UPM-2053https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2050



something morepalatable

UPM-2047 Need pluginhomepageadded toavailable pluginsresource

Resolved Fixed

UPM-2036 Broken AUIStyles - FECRU

Resolved Fixed

UPM-2031 Manage buttondoesn't work onInstall page

Resolved Fixed

UPM-2026 manage pluginpane hasscrewed uplayout

Resolved Fixed

UPM-2025 off-market paidplugin shows asfree

Resolved Fixed

UPM-2023 Move re-styleddownload-install-complete popupinto a dialog

Resolved Fixed

UPM-2022 Dividing borderin plugin infoisn't tall enough

Resolved Fixed

UPM-2021 Add additionaldetails toInstallable plugindetails

Resolved Fixed

UPM-2018 hostStatus.pacUnavailablecomes back asfalse when PACis down

Resolved Fixed

UPM-2016 PACunreachablemessagesdisappears onManage page

Resolved Fixed

UPM-2015 When PAC isdown, we don'tdisplay anyindication of thaton the Find NewPlugins page

Resolved Fixed

UPM-2013 Downloadcounts don'thave commas

Resolved Fixed

UPM-2012 If banner isclicked whencorresponding

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2050https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2047https://ecosystem.atlassian.net/browse/UPM-2036https://ecosystem.atlassian.net/browse/UPM-2036https://ecosystem.atlassian.net/browse/UPM-2036https://ecosystem.atlassian.net/browse/UPM-2036https://ecosystem.atlassian.net/browse/UPM-2031https://ecosystem.atlassian.net/browse/UPM-2031https://ecosystem.atlassian.net/browse/UPM-2031https://ecosystem.atlassian.net/browse/UPM-2031https://ecosystem.atlassian.net/browse/UPM-2031https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2026https://ecosystem.atlassian.net/browse/UPM-2025https://ecosystem.atlassian.net/browse/UPM-2025https://ecosystem.atlassian.net/browse/UPM-2025https://ecosystem.atlassian.net/browse/UPM-2025https://ecosystem.atlassian.net/browse/UPM-2025https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2023https://ecosystem.atlassian.net/browse/UPM-2022https://ecosystem.atlassian.net/browse/UPM-2022https://ecosystem.atlassian.net/browse/UPM-2022https://ecosystem.atlassian.net/browse/UPM-2022https://ecosystem.atlassian.net/browse/UPM-2022https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2021https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2018https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2016https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2015https://ecosystem.atlassian.net/browse/UPM-2013https://ecosystem.atlassian.net/browse/UPM-2013https://ecosystem.atlassian.net/browse/UPM-2013https://ecosystem.atlassian.net/browse/UPM-2013https://ecosystem.atlassian.net/browse/UPM-2013https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012



plugin is notdisplayed,nothing happens

UPM-2010 Fix styling onbuy and trybuttons onManage page

Resolved Fixed

UPM-2009 Add screenshotsto Manage page

Resolved Fixed

UPM-2008 Conform to newAUI styles forblue button

Resolved Fixed

UPM-2007 Re-implementignored pricingtests

Resolved Fixed

UPM-2006 UPM licensechecking codeneeds to allowfor an extra useron EnterpriseHostedConfluence

Resolved Fixed

UPM-2002 Update All UIchanges

Resolved Fixed

UPM-2001 Add Modify andUpdate links toInstalled Pluginsresource

Resolved Fixed

UPM-2000 Add "manage"link toinstall-successresponse

Resolved Fixed

UPM-1999 Changes toAvailable Pluginsresource

Resolved Fixed

UPM-1992 Upload Pluginlink is positionedinsanely inConfluence

Resolved Obsolete

UPM-1989 JS/CSS changesfor dialog styling

Resolved Fixed

UPM-1988 Add informationto thePluginLicensejavadoc aboutusingdeprecatedmethods

Resolved Fixed

UPM-1983 Restylepost-install/update dialogs, addmore

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2012https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2010https://ecosystem.atlassian.net/browse/UPM-2009https://ecosystem.atlassian.net/browse/UPM-2009https://ecosystem.atlassian.net/browse/UPM-2009https://ecosystem.atlassian.net/browse/UPM-2009https://ecosystem.atlassian.net/browse/UPM-2008https://ecosystem.atlassian.net/browse/UPM-2008https://ecosystem.atlassian.net/browse/UPM-2008https://ecosystem.atlassian.net/browse/UPM-2008https://ecosystem.atlassian.net/browse/UPM-2008https://ecosystem.atlassian.net/browse/UPM-2007https://ecosystem.atlassian.net/browse/UPM-2007https://ecosystem.atlassian.net/browse/UPM-2007https://ecosystem.atlassian.net/browse/UPM-2007https://ecosystem.atlassian.net/browse/UPM-2007https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2006https://ecosystem.atlassian.net/browse/UPM-2002https://ecosystem.atlassian.net/browse/UPM-2002https://ecosystem.atlassian.net/browse/UPM-2002https://ecosystem.atlassian.net/browse/UPM-2002https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2001https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-2000https://ecosystem.atlassian.net/browse/UPM-1999https://ecosystem.atlassian.net/browse/UPM-1999https://ecosystem.atlassian.net/browse/UPM-1999https://ecosystem.atlassian.net/browse/UPM-1999https://ecosystem.atlassian.net/browse/UPM-1999https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1992https://ecosystem.atlassian.net/browse/UPM-1989https://ecosystem.atlassian.net/browse/UPM-1989https://ecosystem.atlassian.net/browse/UPM-1989https://ecosystem.atlassian.net/browse/UPM-1989https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1988https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983



plugin/vendorinfo

UPM-1982 Overly largeclickable area forscreenshots

Resolved Obsolete

UPM-1981 Licensed pluginwill not enableafter enteringinvalid licensewhile disabled

Resolved CannotReproduce

UPM-1977 Banner saying"this plugin wasinstalled andalready has avalid license"has gonemissing

Resolved Obsolete

UPM-1975 Include UPMversion inUser-Agentstring

Resolved Fixed

UPM-1969 Improve text onnavigate-from-UPM-to-MACprompt dialog

Resolved Duplicate

UPM-1968 Re-style thedownload andinstall progressdialog

Resolved Fixed

UPM-1967 Plugins web-itemis visible toproject admins inJIRA and shouldnot be

Resolved Fixed

UPM-1962 Fix meta tags invelocity pagesfor JIRA so thatweb-items arehighlightedcorrectly inonDemand.

Resolved Fixed

UPM-1960 Documentpost-install/post-update URLproperties

Resolved Fixed

UPM-1959 Post-installmodal dialog

Resolved Fixed

UPM-1956 CompatibilityPlugin is notupgraded when

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1983https://ecosystem.atlassian.net/browse/UPM-1982https://ecosystem.atlassian.net/browse/UPM-1982https://ecosystem.atlassian.net/browse/UPM-1982https://ecosystem.atlassian.net/browse/UPM-1982https://ecosystem.atlassian.net/browse/UPM-1982https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1981https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1977https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1975https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1969https://ecosystem.atlassian.net/browse/UPM-1968https://ecosystem.atlassian.net/browse/UPM-1968https://ecosystem.atlassian.net/browse/UPM-1968https://ecosystem.atlassian.net/browse/UPM-1968https://ecosystem.atlassian.net/browse/UPM-1968https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1967https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1962https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1960https://ecosystem.atlassian.net/browse/UPM-1959https://ecosystem.atlassian.net/browse/UPM-1959https://ecosystem.atlassian.net/browse/UPM-1959https://ecosystem.atlassian.net/browse/UPM-1959https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956



upgradingMarketplaceplugin

UPM-1955 Move PAC clientinto UPM project

Resolved Fixed

UPM-1954 Marketplaceplugins aremissing requiredpackage forsomeConfluenceversions

Resolved Answered

UPM-1953 return add-onsthat you'vealready installedin the find newadd-ons screen,and make UIchangeaccordingly

Resolved Fixed

UPM-1952 ImplementPlugin Details UIImprovementsFront End

Resolved Fixed

UPM-1947 Use the PluginName (not thefilename) on alldownload andinstall dialogswhen possible

Resolved Fixed

UPM-1945 Plugin Details UIimprovementsfrom Jerry

Resolved Fixed

UPM-1795 Updating unsetplugin license toempty stringyields misleadingsuccessmessage

Resolved Obsolete

UPM-1724 Add apost-install/update action to UPM

Resolved Fixed

Previous Release Notes

Universal Plugin Manager 2.2.X Release Notes

The following table lists the JIRA issues resolved for the 2.2.X release.

(25 issues)JIRA Issues

Type Key Summary Priority Status Resolution

UPM-2039 Universal Plugin Closed Duplicate

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1956https://ecosystem.atlassian.net/browse/UPM-1955https://ecosystem.atlassian.net/browse/UPM-1955https://ecosystem.atlassian.net/browse/UPM-1955https://ecosystem.atlassian.net/browse/UPM-1955https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1954https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1953https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1952https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1947https://ecosystem.atlassian.net/browse/UPM-1945https://ecosystem.atlassian.net/browse/UPM-1945https://ecosystem.atlassian.net/browse/UPM-1945https://ecosystem.atlassian.net/browse/UPM-1945https://ecosystem.atlassian.net/browse/UPM-1945https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1795https://ecosystem.atlassian.net/browse/UPM-1724https://ecosystem.atlassian.net/browse/UPM-1724https://ecosystem.atlassian.net/browse/UPM-1724https://ecosystem.atlassian.net/browse/UPM-1724https://ecosystem.atlassian.net/browse/UPM-1724https://ecosystem.atlassian.net/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20UPM%20AND%20fixVersion%20in%20%2816733,%2016401,%2016394,%2016362,%2016289%29%20AND%20status%20in%20%28Resolved,%20Closed%29&tempMax=1000https://ecosystem.atlassian.net/browse/UPM-2039https://ecosystem.atlassian.net/browse/UPM-2039https://ecosystem.atlassian.net/browse/UPM-2039



Manager will notupdate in JIRA

UPM-2005 OSGi Loaderconstraintviolationinvolvingupm.api.util.Option after installinga Marketplaceplugin and thenupgrading UPMto 2.2.3

Resolved Fixed

UPM-2003 license postbackURL is garbledwhen app has nocontext path

Resolved Fixed

UPM-1996 Exception whenupgrading toUPM 2.0 inFisheye

Resolved Fixed

UPM-1995 UPM 2.0+ notcompatible withany releasedversions ofFishEye/Crucible.

Resolved Fixed

UPM-1978 Maintenanceexpired (andnearlymaintenanceexpired) pluginsare not offeredRenew buttonswhen theyshould be

Resolved Fixed

UPM-1974 a macro orpluign beingexecuted bynon-admin cannot even ask ifthe license isvalid

Resolved Duplicate

UPM-1973 Entry points inlicensed plugins(pre-UPM 2.x)are notaccessible tonon-administrators

Resolved Fixed

UPM-1967 Plugins web-itemis visible toproject admins inJIRA and shouldnot be

Resolved Fixed

http://creativecommons.org/licenses/by/2.5/au/https://ecosystem.atlassian.net/browse/UPM-2039https://ecosystem.atlassian.net/browse/UPM-2039https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2005https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-2003https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1996https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1995https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.atlassian.net/browse/UPM-1978https://ecosystem.a

documentation for universal plugin manager...

Documents