Newer Version for JIRA 6.2.x

[Former user]

Hello,

I'm currently evaluating your plugin and I run into several errors (for ex. in the 500 Session Error or Nullpointer Exeptions).

All those problems seem to be solved in future Versions. But we're only running a 6.2 installation. Is it possible to get a fixed Version for our JIRA Version?

Thanks in advance.

[jost]

Hi,

Would you give us some more information about the problem:

• which version ov The Scheduler Plugin are you using currently

• Do you have any errors in log file? If so, please send this file on our email [e-mail].

Here you can find information about where are the JIRA logs:

• https://confluence.atlassian.com/pages/viewpage.action?pageId=213526227

Regards,

Jacek Ostrowski

[Marcel Munerotto]

Hello,

we are currently using The Scheduler 3.1.3, newest Version for out 6.2 JIRA Version. I get errors like "Cannot find form context in user session!" Or an Website 500 Error "During the last function appeared some technical problems" (Freely Translated from German)

I get those errors mostly when I am trying to edit an existing Scheduled Issue. It happens also at creation but by far not as often.

I sent you an error file to the provided E-Mail Adress.

[jost]

Hello Marcel,

I just received a email from you. Thank you for additional informations and log files - I will keep you updated.

Regards,

Jacek

[jost]

Hi Marcel,

Hi Unfortunately we cannot update this version. However i can support you and find some workaround for this error. From log file i can deduce that you attempt to create Scheduled Job using not without being logged in. Am i right? Youser have to be logged in to perform create action.

Regards

[jost]

Hi Marcel,

Did you managed to solve this problem?

[Marcel Munerotto]

Hello,

I'm sorry. I have been at a customers project for the last week and was unable to keep this issue up to date. After you told me that a logged out user tries to create the scheduled job. I think this is a problem within our system. Resulting from a very special SSO solution we are using.

In my opinion you can close this issue and if I have further issues I can reopen it, or make a new request.

Either way thanks a lot for your help!