Different mappings for Resolved field in Report on Task tableIssue When users create reports on the Task table and apply a filter for the 'Resolved' state, they encounter two separate 'Resolved' options due to differences in how the state is mapped for different task types, resulting in confusion and potentially inaccurate reports if the user doesn't apply workaround filters.ReleaseXP8 and priorCauseThe choice list (sys_choice.LIST) shares the same label "Resolved" under different values for the problem and incident table under the Task Table.ResolutionUpgrade the instance to Xanadu Patch9 to resolve the issue. The different labels used for both tables in XP9 should prevent the confusion caused by the same 'Resolved' label with different values. For instances upgraded to XP9 or above, new values are added to sys_choice table alongside old values. This ensures compatibility with existing records in the problem table that use older values. This is an expected behavior when a report is created on the task table.It is recommended to create a report with individual tables to avoid this issue.