We have seen the issue of a custom field displaying incorrectly in the TaskRay field set occur if the custom field has a Field/API Name that is the same as a field provided in the TaskRay package.
The most frequent occurrence is with the creation of a custom Status field. This issue occurs because TaskRay already uses Status as a Field/API Name behind the scenes. Adding a custom field with the same field name Status would cause all sorts of funny behavior including:
- The custom Status field is not displayed in the TaskRay Task or Project field set.
- A field called 'Archived' or 'Deprecated' may display in the field set.
- No indication that anything is awry on the TaskRay Task or Project object.
Using Status as an example, this is easily solved by changing the custom field name to a string other than Status. For example, you can call it ProjectStatus or TaskStatus. Once this change is made, everything should work as intended again.