FieldName expand workItemFieldTypes

[dotnetninja]

Current FieldName:

"id": "FieldName",
  "name": "Select the field for this control.",
  "description": "The field associated with the control, it will match the value from the rest service's key field.",
  "type": "WorkItemField",
  "properties": {
      "workItemFieldTypes": ["String", "PlainText", "HTML"]
    },
    "validation": {
      "dataType": "String",
      "isRequired": true
    }

It would be awesome if workItemFieldTypes accepted Integer and TreePath types. Validation would have to be altered. However, this would allow for System.IterationID and System.IterationPath to be an acceptable WorkItemControl. This would allow for WorkItem TargetDate to dynamically be populated based on the iteration attributes. Currently WorkItem TargetDate can be set outside of a project teams iteration start and end dates.

[Dedac]

Would the validation need to be altered? I think just adding the types to the list would be enough. I could probably make the change and post a test version if you have a specific org you want to test this out on.

[Dedac]

I see where the validation / type changes would have to occur in the code now. Things like iteration path and setting values that cannot be empty will require some changes to the way and time that field values are set by the extension.

I am not going to have time to spend on this the next couple of weeks, any kind of PR on this would be awesome.

I do really like the suggestion to add to the field types that can be mapped, Thanks