Multi-homed task custom field order changes based on entry project (new UI regression)

1. Summary

Multi-homed task custom field order changes based on entry project (new UI regression)

2. Expected behavior

Each project section within a task should preserve its own custom field order, regardless of which project the task is opened from.

3. Actual behavior

The custom field order across all project sections changes depending on the project from which the task is opened, overriding project-specific field configurations.

4. Impact

  • Cross-functional confusion across teams (teams expect to see the order they set for their project regardless of entry point)

  • Breaks standardized workflows

  • Causes data entry errors / inefficiency

  • Undermines project-level configuration integrity

5. Reproduction steps

  1. Create task and multi-home into 3 different projects (e.g., Project A, Project B and Project C)

  2. Configure different custom field orders in each project (within the Customize > Fields menu)

  3. Open task from Project A → observe field order

  4. Open same task from Project B → observe order changes across both sections

6. Screenshots

These screenshots show the same task with the same project section expanded, opened from three different entry points (three different projects the task is multi-homed in).

Despite viewing the same project’s custom fields, the field order changes depending on the entry point. The field order does not reflect the configured order for that project and instead appears to be influenced by the originating project context.

Hi @Sherilyn_Senior1 , I’ve also noticed the same the past few days and I would consider this a bug actually as it is not performing as it should or at least when this UI changed first launched - I don’t recall the fields being jumbled up based on which project the task is viewed in.

Additionally, is it me or am I noticing LESS fields appear in Project A if the task is viewed from from Project B? (eg. project A has over 40 fields)

Pinging @Forum-team for their escalation to product team, please.
Cc @Stef_O

2 Likes

Thanks for the bump, @Richard_Sather – I reached out to you with some questions so I can look into this.

3 Likes

Hi @Richard_Sather @Stef_O ~ Any luck getting this pushed forward? Need anything else from me?