Jira task management knackered?

Hi,

I've just upgraded to the latest EAP (IU-90.94) and it seems that task management is badly broken. First of all, it could not reimport my previous jira server connection settings. Secondly, after I have created a new jira configuration, it still fails to reload the list of JIRA issues.
I've found this in the startup logs, and we do not have LOCAL-00049 on our server -- looks like a hard-coded value.

2009-10-16 13:24:36,796 [  37154]   INFO - llij.tasks.jira.JiraRepository - HTTP 404 (Not Found)
Could not find issue with issue key LOCAL-00049
com.atlassian.theplugin.jira.api.JIRAException: HTTP 404 (Not Found)
Could not find issue with issue key LOCAL-00049
at com.atlassian.theplugin.jira.api.JIRARssClient.getIssue(JIRARssClient.java:208)
at com.atlassian.theplugin.jira.JIRAServerFacadeImpl.getIssue(JIRAServerFacadeImpl.java:154)
at com.intellij.tasks.jira.JiraRepository.findTask(JiraRepository.java:116)
at com.intellij.tasks.impl.TaskManagerImpl.updateIssue(TaskManagerImpl.java:212)
at com.intellij.tasks.impl.TaskManagerImpl.doActivate(TaskManagerImpl.java:301)
at com.intellij.tasks.impl.TaskManagerImpl.initComponent(TaskManagerImpl.java:486)
at com.intellij.openapi.components.impl.ComponentManagerImpl.a(ComponentManagerImpl.java:17)
at com.intellij.openapi.components.impl.ComponentManagerImpl.access$1200(ComponentManagerImpl.java:28)
at com.intellij.openapi.components.impl.ComponentManagerImpl$ComponentConfigComponentAdapter$1.getComponentInstance(ComponentManagerImpl.java:15)
at com.intellij.openapi.components.impl.ComponentManagerImpl$ComponentConfigComponentAdapter.getComponentInstance(ComponentManagerImpl.java:4)
at com.intellij.util.pico.DefaultPicoContainer.getLocalInstance(DefaultPicoContainer.java:231)
at com.intellij.util.pico.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:218)
at com.intellij.util.pico.DefaultPicoContainer.getComponentInstance(DefaultPicoContainer.java:200)
at org.picocontainer.alternatives.AbstractDelegatingMutablePicoContainer.getComponentInstance(AbstractDelegatingMutablePicoContainer.java:75)
at com.intellij.openapi.components.impl.ComponentManagerImpl.a(ComponentManagerImpl.java:136)
at com.intellij.openapi.components.impl.ComponentManagerImpl.a(ComponentManagerImpl.java:72)
at com.intellij.openapi.components.impl.ComponentManagerImpl.initComponents(ComponentManagerImpl.java:57)
at com.intellij.openapi.components.impl.ComponentManagerImpl.init(ComponentManagerImpl.java:26)
at com.intellij.openapi.project.impl.ProjectImpl.init(ProjectImpl.java:119)
at com.intellij.openapi.project.impl.ProjectManagerImpl.a(ProjectManagerImpl.java:196)
at com.intellij.openapi.project.impl.ProjectManagerImpl.a(ProjectManagerImpl.java:355)
at com.intellij.openapi.project.impl.ProjectManagerImpl.access$200(ProjectManagerImpl.java:294)
at com.intellij.openapi.project.impl.ProjectManagerImpl$6.run(ProjectManagerImpl.java:9)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$3.run(ProgressManagerImpl.java:1)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:2)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$4.run(ProgressManagerImpl.java:1)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:14)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:64)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:87)
at com.intellij.openapi.application.impl.ApplicationImpl$7$1.run(ApplicationImpl.java:7)
at com.intellij.openapi.application.impl.ApplicationImpl$6.run(ApplicationImpl.java:9)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:10)
Caused by: java.io.IOException: HTTP 404 (Not Found)
Could not find issue with issue key LOCAL-00049
at com.atlassian.theplugin.commons.remoteapi.rest.AbstractHttpSession.doConditionalGet(AbstractHttpSession.java:198)
at com.atlassian.theplugin.commons.remoteapi.rest.AbstractHttpSession.retrieveGetResponse(AbstractHttpSession.java:150)
at com.atlassian.theplugin.jira.api.JIRARssClient.getIssue(JIRARssClient.java:196)
... 37 more
2009-10-16 13:24:36,796 [  37154]   INFO - ij.components.ComponentManager - com.intellij.tasks.impl.TaskManagerImpl initialized in 917 ms
Regards,
--
Sergei

3 comments
Comment actions Permalink

Mind you, after the upgrade, all the local SVN changelists were corrupted too:
1. all "track context" settings were reset to 'false' and I had to re-enable them
2. all context information was lost
3. some pending changes were merged from inactive changelists into the active changelist

0
Comment actions Permalink

Task management is under refactoring, including its storage format. But you
should be able to restore your JIRA-associated context by entering issue id
in "Open task" dialog.
As for the exception, could you file a request for it?


0
Comment actions Permalink

Hi,

Submitted an issue to youtrack:
http://youtrack.jetbrains.net/issue/IDEA-25299

There were some other spurious errors in the task management, I submitted these through the feedback dialog.
To be honest, I got used to (maybe even dependent on!) task management in the previous EAP versions, and it worked a treat. This regression and IDEA-25130 do really spoil my daily development in the latest EAP. I hope you'll manage to get it sorted soon.

Cheers,
Sergei

0

Please sign in to leave a comment.