Problem updating Team Calendars 5.1 -> 5.2

[Emmanuel Castanier]

Hi all,

I use daily Team Calendars with Confluence, I tried to update my plugin to 5.2 without succes. After the update no more calendar on the UI, just "$calendarHtml" .

I tried to see in logs, I have some SQL errors :

java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: FK_AO_950DC3_TC_REMINDER_USERS_SUB_CALENDAR_ID

If I go back to 5.1, all work as usual. 

It seems a privileges problem but I never changed anything (I use the default embedded HSQL database).

Help would be appreciated,

Thanks.

[Ram Kumar Aravindakshan _Adaptavist_ · Accepted solution]

Hi @Christopher Gervais 

Instead of using ProjectUpdatedDetailedChangesEvent, why not just use ProjectUpdatedEvent?

The ProjectUpdatedDetailsChangedEvent will not be able to provide you with the required information you are looking for because that event is configured only to return boolean results to verify if there has been any change made to the project properties, which you can see in the Jira Api doc link that you have shared. You can only obtain Avatar and Source Type details when using the ProjectUpdatedDetailsChangedEvent.

Instead, if you use ProjectUpdatedEvent, you can do basic logging if any change has been made to the project's attributes. 

You can retrieve the project's old attributes (i.e. for its last attribute before the change) and its current attributes. In this case, the Project's Key and Name and compare the changes made.

Below is a sample working code for your reference:-

log.warn "=======>>> Old Key: ${event.oldProject.key}, Old Project Name: ${event.oldProject.name}"

log.warn "=======>>> Current Key: ${event.project.key}, Current Project Name: ${event.project.name}"

Below is a screenshot for your reference:-

The code basically prints out the old project key and name along with the current project key and name. From the result, you will see the differences made to the project.

Below is a screenshot of the sample output produced:-

I hope this helps to answer your question. :-)

Thank you and Kind regards,
Ram

[Christopher Gervais]

Thank you Ram! I will use this solution but at first I was trying to find a way with the other event to limit the number of runs the listener will launch