View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0024228||mantisbt||custom fields||public||2018-04-05 06:04||2019-02-22 03:41|
|Target Version||Fixed in Version|
|Summary||0024228: mantis_custom_field_table - add unique index on name|
IMHO creation of two custom fields with the same name has to be blocked not only at application level but also at DB level, that's why adding a unique index on the name could be a good thing.
You can use the same name for fields with different definitions in different projects.
Do you agree that we can set your issue to resolved?
You did not provide any feedback; I am therefore resolving this issue as "no change required".
Feel free to reopen the issue at a later time and provide the requested information.
I apologize for the missing feedback.
One annoyance: the custom field api that allow you to get Custom Field BY NAME is going to return multiple records, then making some kind of implementation difficult.
thanks again for your product
Not sure what I tried when writing this. I thought I was able to create two custom fields with the same name.
So you are right, a unique key would be good to ensure valid data.
Independent from that, using the same name (and also being able to localize it) for different custom fields should be possible when using in different projects.
Thanks, I'm going to check 'custom_field_ensure_name_unique'.
|2018-04-05 06:04||fman||New Issue|
|2019-01-05 10:27||atrol||Relationship added||has duplicate 0025142|
|2019-01-05 10:57||atrol||Status||new => feedback|
|2019-01-05 10:57||atrol||Note Added: 0061151|
|2019-01-30 15:51||atrol||Assigned To||=> atrol|
|2019-01-30 15:51||atrol||Status||feedback => resolved|
|2019-01-30 15:51||atrol||Resolution||open => no change required|
|2019-01-30 15:51||atrol||Note Added: 0061336|
|2019-02-10 08:32||atrol||Status||resolved => closed|
|2019-02-10 11:19||fman||Status||closed => feedback|
|2019-02-10 11:19||fman||Resolution||no change required => reopened|
|2019-02-10 11:19||fman||Note Added: 0061476|
|2019-02-16 16:46||atrol||Note Added: 0061506|
|2019-02-16 16:46||atrol||Assigned To||atrol =>|
|2019-02-16 16:46||atrol||Status||feedback => acknowledged|
|2019-02-16 16:46||atrol||Tag Attached: schema|
|2019-02-17 05:12||fman||Note Added: 0061511|
|2019-02-22 03:41||atrol||Relationship added||related to 0025509|