Vertygo SLA plugin errors

[Darla Sheehan]

Hi,

Having trouble with the right response for a customer on this question.

----------

"We have had Vertygo SLA installed on our JIRA server for quite a long time (5 years+). Recently the plugin has disappeared from the tickets and we aren't quite sure why. Is there any reason you can see why it has disappeared? I am aware that the plugin is no longer supported and hasn't been for quite a few years so it could be a number of things but I was wondering if you can pinpoint why the features have disappeared.

I was aware of the status of the VertygoSLA plugin with Atlassian but I was wondering if you could get any leads on what caused it to stop. It was working a couple of months ago. I know that due to the age of the plugin anything could have caused it to stop but there could be something in the logs that shows whats happening with the plugin?"

------------------

Looking at VertygoSLA -Service Level Agreement on the addon page it is reporting that the License is for an older version and maintenance has expired. The configure button is greyed out that suggests it is probably disabled as the license isnt valid.

We have explianed that Atlassian had acquired VertygoSLA from Valiantys. VertygoSLA is now part of JIRA Service Desk.

But... how can I explain better why it just stopped working for them a few month ago?

Thanks,

Darla

[somethingblue]

Hi Darla,

Did you begin to notice the behavior around the time the license expired?  If so that is most likely the culprit.  You can review the atlassian-jira.log to see if there is anything there that provides any clues as to what caused this to stop working if the license expiry does not coincide.

Cheers,

Branden

[MattS]

Agreed. That's what I saw happen with Vertygo SLA when the license expired for me. Using JSD is your easiest option

[Darla Sheehan]

Thanks Brandon & Matt!

I was not able to see anything in the atlassian-jira.log, but it does not go back months. The license expired "Standard, expires 21/Feb/15", but the customer says it was working up until a few months ago.

I checked - jira/plugins/installed-plugins/, and they have these versions below which are not even listed anymore on this LINK replaced by 7.0.6.12. So maybe that was a buggy version that took longer to stop working after it expired? (Grasping at straws)

• Apr 23 2016 valiantys-base-plugin-1.0.28.jar
• Apr 23 2016 jira-vertygosla-plugin-7.0.6.9.jar

Obviously, we told them the License is for an older version and maintenance has expired, but seem to want to know what would have caused it to totally stop. (I know!)

Thanks!

Darla

[Darla Sheehan]

Only items in atlassian-jira.log - 

2017-09-18 18:50:07,899 http-nio-8080-exec-214 DEBUG admin 1130x7234005x1 d9q0cr - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin [c.a.util.profiling.UtilTimerLogger] [248ms] - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin

2017-09-18 18:50:07,899 http-nio-8080-exec-214 DEBUG admin 1130x7234005x1 d9q0cr - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin [c.a.j.web.filters.ThreadLocalQueryProfiler] PROFILED : 0 keys (0 unique) took 0ms/248ms : 0.0%
2017-09-18 18:50:08,151 Caesium-1-4 DEBUG ServiceRunner [c.a.j.web.filters.ThreadLocalQueryProfiler] PROFILED : 0 keys (0 unique) took 0ms/1433ms : 0.0%
2017-09-18 18:50:08,239 http-nio-8080-exec-213 DEBUG admin 1130x7234007x2 d9q0cr - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin/resource/css/base.css [c.a.util.profiling.UtilTimerLogger] [2ms] - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin/resource/css/base.css
2017-09-18 18:50:08,239 http-nio-8080-exec-213 DEBUG admin 1130x7234007x2 d9q0cr - /plugins/servlet/com.valiantys.refapp.plugin.base.valiantys-base-plugin/admin/resource/css/base.css [c.a.j.web.filters.ThreadLocalQueryProfiler] PROFILED : 0 keys (0 unique) took 0ms/2ms : 0.0%
2017-09-18 18:50:08,592 http-nio-8080-exec-105 DEBUG anonymous 1130x7234009x1 - 34.252.136.12,192.168.128.152 / [c.a.util.profiling.UtilTimerLogger] [92ms] - /
[76ms] - MyJiraHome.execute()
[67ms] - Dashboard.execute()