Error posterior a la actualizacion de jira service desk 2.3.6 a 3.0

[Milena Gonzalez]

Hola a todos!

Quisiera saber que significa y en que repercute el siguiente error que aparece constantemente en los log posterior a la actualizacion que realice sobre la instancia de jira 

1 de los errores

http-nio-8080-exec-23 ERROR administrator 1008x1024x1 1rvyelg 0:0:0:0:0:0:0:1 /secure/admin/workflows/WorkflowDesigner.jspa [c.a.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'ru.andreymarkelov.atlas.plugins.datacollector.conditions.AfterJiraVersion6AdminCondition@2650d9eb' for descriptor: ru.andreymarkelov.atlas.plugins.datacollector:datacollector-configuration_jira6 (null)
java.lang.NoSuchMethodError: com.atlassian.jira.security.JiraAuthenticationContext.getLoggedInUser()Lcom/atlassian/crowd/embedded/api/User;

2 error 

http-nio-8080-exec-22 ERROR administrator 1008x1038x1 1rvyelg 0:0:0:0:0:0:0:1 /secure/admin/workflows/ViewWorkflowTransition.jspa [c.a.plugin.web.DefaultWebInterfaceManager] Could not evaluate condition 'ru.andreymarkelov.atlas.plugins.datacollector.conditions.BeforeJiraVersion6AdminCondition@26f9c002' for descriptor: ru.andreymarkelov.atlas.plugins.datacollector:datacollector-configuration (null)

Quedo atenta a su colaboracion 

[Milena Gonzalez]

Hi Nic,

Thank you for your response, regarding the answer: Validate the update of the complements and they are well.

As I said before these errors occurred after the recommended update according to the migration center in which they indicate that it must be updated first to version 3.0.
But,
¿Is this error significant for the operation of the tool? How can I solve it?

2018-02-09 11:01:07,334 http-nio-8080-exec-15 WARN administrator 661x3784x1 14fx4t3 172.22.4.249 /rest/projects/1.0/project/TSD/lastVisited [c.atlassian.ozymandias.SafePluginPointAccess] A LinkageError indicates that plugin code was compiled with outdated versions.  Unable to run plugin code because of 'java.lang.NoSuchMethodError - com.atlassian.jira.security.JiraAuthenticationContext.getLoggedInUser()Lcom/atlassian/crowd/embedded/api/User;'.

[Nic Brough -Adaptavist-]

I apologise for only being able to answer in English.

This is a problem with the issue history add-on.  Broadly, there are two possible problems:

• It is the wrong version for your version of Jira - try upgrading it via the UPM
• The add-on has a bug - after checking the version, report it to the vendor

It will be worth testing this by disabling the add-on and checking if the problem goes away.