Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Debugging template/workitem issues

Hi
We have made several changes to the Work Item template in our project. At some stage we stopped being able to view work items through the Eclipse UI. The Eclipse log shows:

!ENTRY com.ibm.team.workitem.ide.ui 4 2 2014-03-27 10:22:15.114
!MESSAGE Problems occurred when invoking code from plug-in: "com.ibm.team.workitem.ide.ui".
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: assertion failed:
        at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
        at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
        at com.ibm.team.workitem.common.model.ItemProfile.contains(ItemProfile.java:316)
        at com.ibm.team.workitem.client.internal.util.AuditableBatchResolver.add(AuditableBatchResolver.java:60)
        at com.ibm.team.workitem.client.internal.util.ResolvedWorkItem.add(ResolvedWorkItem.java:365)
        at com.ibm.team.workitem.client.internal.util.ResolvedWorkItem.collect(ResolvedWorkItem.java:291)
        at com.ibm.team.workitem.client.internal.util.ResolvedWorkItem.resolve(ResolvedWorkItem.java:253)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemUIWorkingCopy.resolve(WorkItemUIWorkingCopy.java:231)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInput.resolveAuxiliaryItems(WorkItemEditorInput.java:254)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInput.access$4(WorkItemEditorInput.java:244)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInput$1.run(WorkItemEditorInput.java:180)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInput.fetchAll(WorkItemEditorInput.java:153)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInput.getWorkingCopy(WorkItemEditorInput.java:126)
        at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditorInputFuture$1.runProtected(WorkItemEditorInputFuture.java:86)
        at com.ibm.team.foundation.client.util.FoundationJob.run(FoundationJob.java:68)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

We cannot revert the template because ( I think this the fields that have been changed/added are in use) and now RTC is really unusable for our development team.

The changes were made in RTC level 4.0.2 and 4.0.3. The server has just been upgraded to 4.0.6 which has not fixed the issue.

Any guidance on how we might debug this (and fix!) this would be very much appreciated.

0 votes



One answer

Permanent link
1. First test using the webui.  If the problem does not persist, would suggest opening a PMR.
2. I would suggest reviewing all the attributes to ensure they do not reference a deleted / archived artifact.
3. Review the attributes in the eclipse presentation editor to see if any of them are flagged with an error/warning message.

0 votes

Comments

Hi Abraham

We have tested the web ui and it's fine. I will have a closer look at the attributes, thank you.

We have already opened a PMR as this is having a fairly severe impact on our development process. :-/


We are finding it very hard ti debug because there is so little in the log.

Zoe

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Mar 27 '14, 7:03 a.m.

Question was seen: 5,095 times

Last updated: Mar 27 '14, 1:14 p.m.

Confirmation Cancel Confirm