Done
Details
Assignee
Andrii PaiasAndrii Paias(Deactivated)Reporter
Dima TkachenkoDima TkachenkoLabels
Priority
P3Story Points
3Sprint
NoneDevelopment Team
SpitfireFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Andrii Paias
Andrii Paias(Deactivated)Reporter
Dima Tkachenko
Dima TkachenkoLabels
Priority
Story Points
3
Sprint
None
Development Team
Spitfire
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 4, 2019 at 1:08 PM
Updated October 18, 2019 at 1:24 PM
Resolved October 18, 2019 at 1:24 PM
Custom field object definition contains data applicable to any CF type as long as type specific one (see also customField.json):
For instance "name", "refId", "helpText" attributes applicable to all custom fields, but "textField" attribute only make sense to SHORT_TEXT and LONG_TEXT custom field types – for the rest it's meaningless.
Right now it's possible to store CF with this meaningless information. This should be fixed by cleaning up CF content depending on its type