Changes in atlassian-plugin.xml require JIRA restart Edited

Hi everyone,

I am developing a JIRA report plugin and I need to add another property (field) into report configuration page. However after I do that, I have to restart JIRA for changes to take effect. I can survive this while development, however restarting live system for just installing new version of a plugin seems to be too much.

How can I solve this? Non of plugins from market requires this, so there must be a way. 

For your reference, I've tried so far:

  1. Changing plugin version in pom.xml
  2. Ctrl+F5 on plugin management page
  3. Deleting/installing plugin from scratch

Non of that works. I've seen a lot of questions on the subject, but there were no solutions.

Here is my atlassian-plugin.xml:

<atlassian-plugin key="${atlassian.plugin.key}" name="${project.name}" plugins-version="2">
<plugin-info>
<description>${project.description}</description>
<version>${project.version}</version>
<vendor name="${project.organization.name}" url="${project.organization.url}"/>
<param name="plugin-icon">images/pluginIcon.png</param>
<param name="plugin-logo">images/pluginLogo.png</param>
</plugin-info>
<!-- add our i18n resource -->
<resource type="i18n" name="i18n" location="report2"/>
<!-- add our web resources -->
<web-resource key="report2-resources" name="report2 Web Resources">
<dependency>com.atlassian.auiplugin:ajs</dependency>
<resource type="download" name="report2.css" location="/css/report2.css"/>
<resource type="download" name="report2.js" location="/js/report2.js"/>
<resource type="download" name="images/" location="/images"/>
<context>report2</context>
</web-resource>
<report name="Monitor Report" i18n-name-key="monitor-report.name" key="scope-monitor-report" class="com.reports.jira.reports.Monitor">
<description key="monitor-report.description">Monitor Report</description>
<resource name="view" type="velocity" location="/templates/reports/monitor-report/view.vm"/>
<resource name="view.css" type="download" location="css/view.css"/>
<resource name="i18n" type="i18n" location="MonitorReport"/>
<label key="monitor-report.label"/>
<properties>
<property>
<key>build</key>
<name>monitor-report.build.name</name>
<description>monitor-report.build.description</description>
<type>select</type>
<values class="com.reports.jira.reports.BuildParamsValuesGenerator"/>
</property>
<property>
<key>bsa</key>
<name>monitor-report.bsa.name</name>
<description>monitor-report.bsa.description</description>
<type>user</type>
<values class="com.atlassian.jira.issue.customfields.impl.UserCFType"/>
</property>
</properties>
</report>
</atlassian-plugin>

 

4 answers

0 votes
Tayyab Bashir Community Champion Oct 27, 2017

Hi,

Often times cache keeps serving changes from the previous versions.
(Although this happens to me after when dealing with changes in JavaScript)

But you could still try by deleting all the cached files and images from your browser to see if it picks up the changes or not. 

Hi,

Thanks for your reply. Actually I already tried this already and just in case tried it again right now. It doesn't help. 

An update:

If I install a newer version of the plugin, the source code is being updated, but the configuration form of the plugin not. E.g. as I'm adding a new property and do some checks in code, I get an error as there is no parameter specified in the URL, but it is expected in the code. So if I add parameter to the URL, I get result from the new code. 

Example:

it looked like this before:

ConfigureReport.jspa?build=REL-43&selectedProjectId=11012

And when I press Next after report configuration I get NullPointerException. 

So now it should look like this:

ConfigureReport.jspa?build=REL-43&bsa=&selectedProjectId=11012

OR

ConfigureReport.jspa?build=REL-43&bsa=georgie&selectedProjectId=11012

and I get correct results. 

Anyone? Any help? Pleeeaaase....

0 votes

How are you developing it? Are you using atlas-run/debug in the sdk? That should be by default disabling caching (which it sounds like you're hitting).

Hi Daniel,

No, I use atlas-package and then install target jar onto my JIRA instances. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,950 views 12 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot