Story point selection is disabled

Before you copied the process over, did you ever introduce an attribute with the id "com.ibm.team.apt.attribute.complexity"? The problem there would be that this attribute still exists in that project area independently from the process configuration and it would still have the same type you originally chose. If that type is not "complexity" as for the enumeration in the Scrum template the editor will still use that old type which currently cannot be changed once an attribute was introduced.

As a guess: could you check if there is a custom attribute with the id "com.ibm.team.apt.attribute.complexity" in your Eclipse Way template (see Process Templates view) and check if its type is the same as the one in the Scrum process you copied over?

Christof
Jazz Work Item team


Bryan Hunt wrote:

I have a project area that was initially configured with the Eclipse Way
process. I replaced the process with that from another project area
that was configured for Scrum. Everything seems to be working except
for story points - the combo is disabled. The story points for the
project area that was originally configured for Scrum works just fine.
I even took the process from the non-working project area and copied
over the working project area, and it worked. There are no messages in
the client or server error logs. Any ideas on how to debug this?

Bryan

Christof, Thank you for your reply. That's exactly my problem. Here
is the entry from my old Eclipse Way process:

<customAttributes>
<customAttribute>
</customAttributes>

I fixed my problem by changing the id in my Scrum process to:

<customAttributes>
<customAttribute>
<customAttribute>
</customAttributes>

with the corresponding change to:

<presentation>

and it seems to be working. Would this problem be worthy of a jazz work item?

Bryan


On 2008-09-19 07:39:58 -0500, Christof Marti <christof_marti> said:

Before you copied the process over, did you ever introduce an attribute
with the id "com.ibm.team.apt.attribute.complexity"? The problem there
would be that this attribute still exists in that project area
independently from the process configuration and it would still have
the same type you originally chose. If that type is not "complexity" as
for the enumeration in the Scrum template the editor will still use
that old type which currently cannot be changed once an attribute was
introduced.

As a guess: could you check if there is a custom attribute with the id
"com.ibm.team.apt.attribute.complexity" in your Eclipse Way template
(see Process Templates view) and check if its type is the same as the
one in the Scrum process you copied over?

Christof
Jazz Work Item team


Bryan Hunt wrote:
I have a project area that was initially configured with the Eclipse
Way process. I replaced the process with that from another project
area that was configured for Scrum. Everything seems to be working
except for story points - the combo is disabled. The story points for
the project area that was originally configured for Scrum works just
fine. I even took the process from the non-working project area and
copied over the working project area, and it worked. There are no
messages in the client or server error logs. Any ideas on how to debug
this?

Bryan