Owned by field on on an RTC work item
Accepted answer
Hi Sean,
the behavior you are seeing is as designed.
However, you can use a default value attribute customization to set owner to the logged in user. here is how you can go about it:
1. Project Configuration > Configuration Data > Work Items > Attribute Customization > Default Values > Add new default value
2. Select User as Provider and Authenticated User under configuration
3. Switch to Types and Attributes > Select any Type > Select Owned By attribute > set the default value to the one just created.
and that's it, now when a new work item is created, the person who creates it (basically the logged in authenticated user) will show up as Owning the item.
You may want to keep in mind that the Owned By attribute is a built in attribute and hence its shared among all types and so the effect would be seen in all work item types. Not to worry, since its only a default value and can be altered by the user as required.
hope it helps.
the behavior you are seeing is as designed.
However, you can use a default value attribute customization to set owner to the logged in user. here is how you can go about it:
1. Project Configuration > Configuration Data > Work Items > Attribute Customization > Default Values > Add new default value
2. Select User as Provider and Authenticated User under configuration
3. Switch to Types and Attributes > Select any Type > Select Owned By attribute > set the default value to the one just created.
and that's it, now when a new work item is created, the person who creates it (basically the logged in authenticated user) will show up as Owning the item.
You may want to keep in mind that the Owned By attribute is a built in attribute and hence its shared among all types and so the effect would be seen in all work item types. Not to worry, since its only a default value and can be altered by the user as required.
hope it helps.
2 other answers
Hi, Sean,
Yes, that's correct behavior. Here is our example to show you why.
In our development environment, requirements analyst would usually create Story cards and iteration manager would decide which cards go in next iteration and then Developers would assign themselves as the owner.
So setting the creator as the owner by default doesn't really apply to everyone.
Hope that helps. Thanks.