Error while trying to access scheduler "Manage Access to Scheduled Issues" page
I have installed a trial version of scheduler. I am currently using jira version v6.4.10. The scheduling works perfect however I keep getting errors each time I try to manage access to scheduled issues " page. Oops, you've found a dead link. I uninstalled the addon. Did a re-install and the error still exists. We are using an oracle database running on redhat linux.
Comments (12)
-
-
Hello,
MrTons have right. I don't know which version are you using currently however it look like bug from older version of plugin. Installation the nevest version of The Scheduler Plugin (TSP 3.2.13) avaliable for your version of JIRA should fix this bug.
You can download this version from:
https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/versions
Please let us know whether this solve this issue.
-
@ostrowskij thanks for the quick response. I installed the new version of the plugin but I still have the same error. I am very interested in purchasing the plugin because its the only one I can find that meets our requirements if I can get it to work. any more suggestions on how to make it work? Tonny
-
Hi,
It would be helpful if you could send the atlassian-jira.log file at support.atlassian@tt.com.pl.
https://confluence.atlassian.com/pages/viewpage.action?pageId=213526227
-
- attached atlassian-jira.log
-
- attached atlassian-jira.log.1
-
Hi,
I suppose that the problem is due to your database. What type and version of database are you using?
-
I am using Oracle 11.2.0.2 running on Red Hat Linux 6.
-
I was able to resolve this issue using this process 1.Uninstall the plugin using plugin manager. 2.stop jira application 3.Purge existing tables that begin with the name "AO_A406ED_*xxxxxxxx" 4. Drop sequences that begin with "AO_A406ED_xxxxx" 5.Start jira 6.Re-install the plugin using plugin manager. Hope this helps somebody else. Tonny
-
Hi,
Thank you for this description. Let us know if you will have other problems or questions.
-
- changed status to resolved
-
- edited description
- changed status to closed
- Log in to comment
This issue was supposed to have been fixed in ver Version 3.2.13 . But I am still getting the same issue with Version 3.2.13