[closed] Missing image icons for iteration plans displayed in Web UI

Not sure if this problem is caused by missing SSL certification?

On 3/17/10 7:37 PM, stevenyj wrote:

Hi,

My client migration their project area from RTC 1.0 to 2.0. But now
when they tried to view their iteration plans on Web UI using IE7,
the image icons for their iteration plans were missing. IE shows the
broken image links.

If they are using Firefox, no broken image links were shown, but the
actual icons were not displayed neither.

I asked them to check the eclipse client, and confirmed that under the
Project Area -> Plans -> Current Plans folder, all the iteration
plans are displayed without plan image icon.

According to my client, this issue only showed up to their migrated
project area (which was initially created using RTC 1.0 Scrum
template). Any project area created fresh in 2.0 is fine.

Wonder if this is a migration issue. Any suggestion on how to restore
those plan image icon back to the project area?

Thanks!

Did you customize the plan types in that project area? In 2.0 (given
that you are using 2.0 and not 2.0.0.2) there is a problem with plan
type icons. Please check if you have plantype-element in the process
configuration source and what the icon-attribute reads.

--
Cheers, Johannes
Agile Planning Team

Hi Johannes,

My client is using RTC 2.0.0.2, and they have customize the project area in 1.0.x before, not sure if they have touched the plan type.

Is it still valid for them to check "plantype-element in the process configuration source"?

Thanks!

Hi Johannes,

Here is what my client has in his project area process configuration source:
<configuration-data xmlns="http://com.ibm.team.apt.configuration/planTypes" id="com.ibm.team.apt.configuration.plantypes">
<plantype icon="bundleentry://59/icons/obj16/release_plan.gif" id="com.ibm.team.apt.plantype.release" name="Team Release Plan">
<planitems definition="com.ibm.team.apt.planitems.releasePlan"/>
<planmodes default="com.ibm.team.apt.viewmodes.internal.iteration">
<planmode definition="com.ibm.team.apt.viewmodes.internal.iteration"/>
<planmode definition="com.ibm.team.apt.viewmodes.internal.teamWorkBreakdown"/>
</planmodes>
<planchecks>
<plancheck definition="com.ibm.team.apt.plancheck.requiredAttribute"/>
</planchecks>
</plantype>
<plantype icon="bundleentry://59/icons/obj16/iteration_plan.gif" id="com.ibm.team.apt.plantype.default" name="Iteration Plan">
<planitems definition="com.ibm.team.apt.planitems.iterationPlan"/>
<planmodes default="com.ibm.team.apt.viewmodes.internal.workBreakdown">
<planmode definition="com.ibm.team.apt.viewmodes.internal.plannedTime"/>
<planmode definition="com.ibm.team.apt.viewmodes.internal.workBreakdown"/>
<planmode definition="com.ibm.team.apt.viewmodes.internal.developersTaskboard"/>
</planmodes>
<planchecks>
<plancheck definition="com.ibm.team.apt.plancheck.schedulingCheck"/>
<plancheck definition="com.ibm.team.apt.plancheck.requiredAttribute"/>
</planchecks>
</plantype>
<plantype icon="bundleentry://59/icons/obj16/release_plan.gif" id="com.ibm.team.apt.plantype.release.project" name="Project Release Plan">
<planitems definition="com.ibm.team.apt.planitems.projectReleasePlan"/>
<planmodes default="com.ibm.team.apt.viewmodes.internal.team">
<planmode definition="com.ibm.team.apt.viewmodes.internal.iteration"/>
<planmode definition="com.ibm.team.apt.viewmodes.internal.projectWorkBreakdown"/>
</planmodes>
<planchecks>
<plancheck definition="com.ibm.team.apt.plancheck.requiredAttribute"/>
</planchecks>
</plantype>
</configuration-data>

Any suggestion how to correct his problem?

Thanks for the help!

Here is solution suggested by our development:
Note that the icon-attribute of the plantype-element is wrong (we had a defect in that area). Instead of

<plantype icon="bundleentry://59/icons/obj16/release_plan.gif" id="com.ibm.team.apt.plantype.release" name="Team Release Plan">

it should read

<plantype icon="icons/obj16/release_plan.gif" id="com.ibm.team.apt.plantype.release" name="Team Release Plan">

So the fix is remove the string bundleentry://<number>. Then it will work again.