[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Description:
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* 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___
* edit an existing data type
* remove (not delete) an existing data type
... so that I can use the data type when creating a decision related asset.
was:
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* 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___
* edit an existing data type
* remove an existing data type
so that I can use the data type when creating a decision related asset.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * 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___
> * edit an existing data type
> * remove (not delete) an existing data type
> ... so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Description:
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* 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___
* edit an existing data type
* remove an existing data type
so that I can use the data type when creating a decision related asset.
was:
As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
- selecting an existing data type
- creating a new one
- editing an existing data type
- deleting an existing data type
so that I can use this data type to make some decision.
Notes (functional requirements)
* solution that supports PHIR and MISMO schema models and similarly complex models.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * 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___
> * edit an existing data type
> * remove an existing data type
so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2728:
--------------------------------------------
[~uxdlc], ok (as discussed in Slack).
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
> Notes (functional requirements)
> * solution that supports PHIR and MISMO schema models and similarly complex models.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2714) Future: Dialog to name test and define bindings (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2714?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2714:
-------------------------------------
[~Rikkola] [~danielezonca] Could you let me know what fields would be needed for the other types: DMN, Process, etc.? Thanks
> Future: Dialog to name test and define bindings (UX)
> ----------------------------------------------------
>
> Key: DROOLS-2714
> URL: https://issues.jboss.org/browse/DROOLS-2714
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
> Attachments: Add-future1c.png, Add-simple1.png, Add-simple1b.png
>
>
> As a business user I want to +Add+ a scenario test asset, so that I perform simulation tests against certain (decision) asset types, including: Rules, DMN, and Processes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2696) MVP Dialog to name test and define bindings (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2696:
-------------------------------------
[~Rikkola][~danielezonca] The test asset name issue is a separate jira, this one just covers the bindings. I'd like to mark this as Done if the mocks look okay, please let me know. Thanks!
> MVP Dialog to name test and define bindings (UX)
> ------------------------------------------------
>
> Key: DROOLS-2696
> URL: https://issues.jboss.org/browse/DROOLS-2696
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
> Attachments: Add-simple1.png, Add-simple1b.png
>
>
> As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ 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?
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
> Notes (functional requirements)
> * solution that supports PHIR and MISMO schema models and similarly complex models.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Issue Type: Story (was: Task)
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
> Notes (functional requirements)
> * solution that supports PHIR and MISMO schema models and similarly complex models.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years