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
-
Create task and multi-home into 3 different projects (e.g., Project A, Project B and Project C)
-
Configure different custom field orders in each project (within the Customize > Fields menu)
-
Open task from Project A → observe field order
-
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.


