null error after upgrade to 7.3.6

[Edmond Ho]

After upgrading from JIRA 6.4.10 to 7.3.6, we're seeing a lot of scheduler errors. Here's the log:

[c.a.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'pl.com.tt.thescheduler.utils.SchedulerPermissionCondition@620e2055' for descriptor: pl.com.tt.jira.plugin.theschedulerpro:schedule-issue (null)

We haven't received any word that there are broken scheduled issues nor any users complaining about permissions - so priority classified as minor.

[Dominik M.]

Dear Edmond,

I need some more information - can you please inform me about those things as well:

• what is the database used in this instance (and what's its version)?
• what scheduler version do you use?

Please be advised - if you use version older than 5.0.2, then please update to the latest version 5.0.2 and let us know if this helped.

Best regards, Dominik Maciejewski Support Team Transition Technologies PSC Sp. z o.o.

[Edmond Ho]

Hi Dominik,

We are already using TheScheduler v5.0.2. Our DB = 10.1.14-MariaDB

[Dominik M.]

Dear Edmond,

We have just released version 5.0.4 of The Scheduler Plugin.

Please update the plugin through the add-ons page or download from the marketplace: https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/versions and let me know if this helped in any way.

Many thanks, Dominik

[Edmond Ho]

Thanks for the update - I'll likely have to deploy it Friday evening during less critical hours.

[Dominik M.]

Dear Edmond,

I'm writing to ask for a feedback, if the issue was perhaps resolved by upgrading the add-on?

Many thanks, Dominik

[Edmond Ho]

Hi Dominik,

The new app version was applied, but we are still seeing the error come up. Can't determine a rate change, but seems less by a minuscule margin?. I'm actually working with the business unit that's using the application right now to figure out if there are any incorrect settings on our part since the upgrade to 7.3.6 from 6.4.10. I'll close the ticket for now, but I'll update you with any developments.

[Edmond Ho]

Hi Dominik,

An update of sorts: Checking a performance logging tool, it looks like there are 2 errors relating to thescheduler that's triggering 30k/day.

1. Could not evaluate condition 'pl.com.tt.thescheduler.utils.SchedulerPermissionCondition@4f20c617' for descriptor: pl.com.tt.jira.plugin.theschedulerpro:schedule-issue (null)
2. Could not evaluate condition 'pl.com.tt.thescheduler.utils.SchedulerPermissionCondition@3c7ad260' for descriptor: pl.com.tt.jira.plugin.theschedulerpro:scheduled-issues-project-tab-panel-link (null)

The performance monitoring tool points out that this seems to be some security check that's happening on our open-source/public tickets. The user-action performed is 'loading LPS-xyz' for instance.

It's currently populating 90% of our log items. Again, it doesn't seem critical as our business units are not complaining about lack of functionality. So this bug is primarily affecting the admin (myself)

[Edmond Ho]

Hi Dominik,

I noticed something else - that all these log items are being triggered a majority of the times by bots. This happens because being an open-source company, our permissions for our open-source projects are set to 'anyone'. But, everyone does not have access to create tickets or anything - is this the permission check that's being run and verified by thescheduler? Do I need to disable view permissions for 'anyone' ?

Again, there doesn't seem to be anything breaking. But it makes identifying problems from the logs difficult when >90% are identical and from this plugin.

[Dominik M.]

Dear Edmond,

I have just received an information that the reported errors were tested and necessary amendments are to be included in the next add-on's release. Hopefully they will eliminate the problems. Sorry for the inconvenience that you have with this version. If there's anything we can assist in regards to this issue, then please do not hesitate to inform here.

Many thanks, Dominik

[Edmond Ho]

Thanks Dominik for the update.

My colleague will apply the updated version and will get back to you if it fixes this problem. I think there's some downtime scheduled in the next week or so to apply the update.

[Edmond Ho]

Hi Dominik,

Can you please specify what version # the fix will be included?

Thanks, Ed

[Dominik M.]

Hello,

Sure, the version in which the fix is to be included is v5.0.7

Many thanks, Dominik

[Łukasz Modzelewski]

Please update to latest version 5.0.7 - this should fix this problem.

Cheers,

Łukasz