[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2728: ------------------------------------- [~karreiro] Thanks for adding the info to the jira. If I'm understanding this correctly, then I think we should break this design story into 2 jiras. One would cover the simple and (simple) structured use cases. The other would cover the complex or "compound" data type, and all that comes with that. The jira user stories might go like this: One jira: As a practitioner I want to be able to: * select an existing data type * create a simple or structured data type * edit an existing data type * remove an existing data type so that I can use the data type when creating a decision related asset. ——— Another jira: * create a “compound” (or complex) data type, easily. * expand/collapse views of compound data types, so that I can___ * navigate between levels in a compound data type, so that I can___ wdyt? -- This message was sent by Atlassian JIRA (v7.5.0#75005)