Numeric values for the "State" field in the Task table and its child

[JB SuW]

Hello everyone,
we are considering creating lists based on the task table for our leadership teams.
These lists are intended to serve purely as monitoring tools.

During testing, we noticed that numeric values in the status field, for example, in cases and incidents, can be identical while representing different meanings.
This can lead to issues when filtering the lists.
For instance, the incident state "In Progress" has the value 2, while the case state "Work in Progress" also uses the value 2.

Would there be any issues if we modified these numeric values to be unique across different task types?

Regards

Jonas

[Ankur Bawiskar]

@JB SuW 

I will recommend not touching the choice values for the OOTB state choice values.

We never know where all it's used (business rule, client scripts etc) and it might break the functionality as well.

Anyhow when user does the filtering they can always select the State choice label while applying filter conditions.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Chaitanya ILCR]

Hi @JB SuW ,

there would a lot issues if you change the values

the existing data and logic would be impacted you have to calculate all these potential downsides before changing the values you can change the labels without any issues but with values you have to consider so many things especially the OOB choices 

incident and case have their own choices you can put a filter like task type is incident or case and filter further or  we can go to the individual tables and filter the data 

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

[Mark Manders · Accepted solution]

This issue is caused a long time ago when 'task' was introduced as the super parent of all task types and it should have been resolved then, but it wasn't, causing this issue when you report on state on task level. 

DO NOT change the values, because you will break the OOB processes, since they are running on the values. 

Either report on task type level, or create reports per task (or accept that this is a huge inconvenience that can't/won't be fixed).