This is part of story #9090: have computed fields compatible with artifact links v2 How to test this: In the tracker administration, Given an existing computed field, whatever its mode ("fast compute" or not) and given the field's name was NOT the same as the "target field" (e.g. target field was empty), when you edit it, then you will see a warning to set the "target field" equal to the computed field's name. This also changes the deprecation warning: Given an existing computed field, whatever its mode and given the field's name was NOT the same as the "target field": - as siteamdin, when you go to the platform's Tracker administration page, then this field will be listed in the deprecated fields report - as tracker admin, when you go to the Trackers main page, then a warning to update the deprecated fields will be displayed and the computed field will be listed in it - as tracker admin, when you go to the Tracker's administration page, then a warning to update the deprecated fields will be displayed Change-Id: I633b8db9f81f57098d15effda994ea5d80ab7bcc

+52 −24

Author

Joris MASSON (jmasson) 2016-06-07 16:54

Committer

Joris MASSON (jmasson) 2016-06-08 10:30

Hash 2176776039ae0fd62a48393061a3fcbfdae6774f

Parent 655fc31d875e81d155105a5b76f46682e13ba26c

Reference git #tuleap/stable/2176776039ae0fd62a48393061a3fcbfdae6774f