Hello:
I hope I'm asking this in a way that makes sense.
My teams use Mantis in a variety of ways and often request per-project customizations. I've been investigating that, and I've got a good understanding on how customizing them works.
One question did arise, though:
Do the enumeration values have meaning in themselves? For example, is their order ever important? In other words, does their ordinality matter? Or are enums' values used purely as unique identifiers in the database?
I hope that's clear and a reasonable question. Please feel free to point me to the docs if I've overlooked something.
Thanks,
Greg
Is enum order important?
Moderators: Developer, Contributor
Re: Is enum order important?
Some enum values have a special meaning, e.g. the values of the status enum.
For example there is a configuration option $g_bug_resolved_status_threshold.
A bug is considered to be resolved whenever the status value is greater than $g_bug_resolved_status_threshold.
For example there is a configuration option $g_bug_resolved_status_threshold.
A bug is considered to be resolved whenever the status value is greater than $g_bug_resolved_status_threshold.
Re: Is enum order important?
Thanks, atrol! That's really useful knowledge.
Greg
Greg