Ability to modify creator

Hi,
Here's the scenario:

A user creates a work item and is emailed with all the events on the
work item. That user would then like to hand ownership of it (from a
creator point of view) to someone else. Either because: they take a job
in another team within the project area are no longer have an interest
in the work item. Or, perhaps they leave the company and an admin or
scrum master role needs to reassign the 'creator' role to someone else.

Looks like this in the process configuration could be changed but when I
changed it it didn't have an affect on the GUI.

property key="readonly" value="true"/

Thanks,
Jeremy

It all depends on how one interprets the fields, but commonly "creator"
is not a role ... it's a historical fact (and therefore readonly). The

"owner" of the workitem is a separate field, and it sounds like that is
the field that you should be working with.

Cheers,
Geoff

Jeremy Hughes wrote:
Hi,
Here's the scenario:

A user creates a work item and is emailed with all the events on the
work item. That user would then like to hand ownership of it (from a
creator point of view) to someone else. Either because: they take a
job in another team within the project area are no longer have an
interest in the work item. Or, perhaps they leave the company and an
admin or scrum master role needs to reassign the 'creator' role to
someone else.

Looks like this in the process configuration could be changed but when
I changed it it didn't have an affect on the GUI.

property key="readonly" value="true"/

Thanks,
Jeremy

On 11/12/2008 17:52, Geoffrey Clemm wrote:
It all depends on how one interprets the fields, but commonly
"creator" is not a role ... it's a historical fact (and therefore
readonly). The

That's a fair point. What I'd like is to allow the creator to disengage
from the process of completing the work item for whatever reason. They
can remain the creator, but they'd like to stop receiving emails to do
with the work item - because it is no longer any of their business. Put
another way, what is behind the decision to prevent the creator from
unsubscribing from a work item?

"owner" of the workitem is a separate field, and it sounds like that
is the field that you should be working with.

Cheers,
Geoff

Jeremy Hughes wrote:
Hi,
Here's the scenario:

A user creates a work item and is emailed with all the events on the
work item. That user would then like to hand ownership of it (from a
creator point of view) to someone else. Either because: they take a
job in another team within the project area are no longer have an
interest in the work item. Or, perhaps they leave the company and an
admin or scrum master role needs to reassign the 'creator' role to
someone else.

Looks like this in the process configuration could be changed but
when I changed it it didn't have an affect on the GUI.

property key="readonly" value="true"/

Thanks,
Jeremy

On 11/12/2008 17:52, Geoffrey Clemm wrote:
It all depends on how one interprets the fields, but commonly "creator"
is not a role ... it's a historical fact (and therefore readonly). The

That's a fair point. What I'd like is to allow the creator to disengage
from the process of completing the work item for whatever reason. They
can remain the creator, but they'd like to stop receiving emails to do
with the work item - because it is no longer any of their business. Put
another way, what is behind the decision to prevent the creator from
unsubscribing from a work item?

In the User Editor (RTC Eclipse UI) you have fine-grained control over
what notification e-mails are being sent to you. There you can disable
notifications for work items that you created.

This doesn't cover the case of a single work item, though, and the

settings currently do not apply to feed notifications. Also, the
configuration tabe is not yet available in the Web UI.