I’m a little confused about how this works or how I should set up to work better: I have a project with a task, priority listed as “medium.” That task, when it appears on “My Tasks” does NOT have a priority listed. They both have priority fields…why don’t they map over from one to another? Is there a way to make them connected?
Chrissy, Can you confirm if both the project and your My Tasks are using a “library” defined field? In order to share values across projects, my understanding is that they should be defined as a shared library field, instead of a “locally” defined field in the project. This is my experience anyways! ~jenn
To know if you are using the same field, there is an easy test: open a task assigned to you that also belongs to the project → if you see 2 “Priority” fields in the task pane on the right, then you did not choose a field in the library but instead created 2 fields. Let us know!
I’m having the same issue here. When I add the Priority field in certain projects, it appears as a distinct field to the ‘My Tasks’ Priority field.
I am not doing anything different in the way I add/remove the fields, I am not creating a custom field and specifically naming it ‘Priority’. I don’t understand why in some projects it is being added as as the My Tasks variant, and others it is appearing as a separate standalone field (ie. I can see Priority appear both as a ‘My Tasks Field’ and as a ‘Field’ within each task). It doesn’t appear to matter whether the project is individual or shared - I am getting mixed results across them.
There are local custom fields (local to a project or your My Tasks) and org-wide custom fields shared in your org’s library. You could have one Priority shared field and one or more local fields and they’re not the same field.
For your purpose, only used the shared field. Replace in your My Tasks or other projects the local one with the shared one.