ScriptException Viewing Sprint Backlog Plan

This is most probably due to a incorrect configuration. Unfortunately, Agile Planning in RTC2.0 does not fail gracefully when simple configuration mistakes - such as no longer defined priorities etc - are present.
This is all fixed for the 2.0.0.1 release.

In the meantime, please try the workaround described here:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/86142

similar to the problem above is this one, where the same workaround applies, just for work item types:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87503

please let us know if the problem did not go away after applying the workaround.

I'm sorry for the inconvenience this has caused.

--
MikeS
Jazz Agile Planning team

Mark Ingebretson wrote:

We have a Sprint Backlog plan in V2.0 for a team area which causes an
error to pop up when attempting to view the Planned Items tab:

An error has occurred. See error log for more details.
com.ibm.team.apt.internal.common.scripting.ScriptException

There are about 14 of these errors in a scrollable list on the popup. A
couple of them are java.lang.NullPointerException.

I don't see anything in the server system log.

Each time I switch the View As setting I get another identical popup.

A query for the plan's team and iteration shows 32 work items.

Any ideas on what can cause a Script Exception? We're running a
modified version of Scrum 2.0.

Thanks,

Mark Ingebretson

Michael Schneider wrote:

This is most probably due to a incorrect configuration. Unfortunately,
Agile Planning in RTC2.0 does not fail gracefully when simple
configuration mistakes - such as no longer defined priorities etc - are
present.
This is all fixed for the 2.0.0.1 release.

In the meantime, please try the workaround described here:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/86142


similar to the problem above is this one, where the same workaround
applies, just for work item types:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87503


please let us know if the problem did not go away after applying the
workaround.

I'm sorry for the inconvenience this has caused.

Mike,

Thanks for your response, that got us on the right track. I think your
work-arounds kind of assume the issue is priority-related, since there
was a change there in Scrum 2.0. The issue we found had to do with
impediments, and the mapping of the V1 states to V2 states. We've
updated and re-mapped our state field data successfully.

Thanks,

Mark