[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2707:
--------------------------------
Labels: UX UXTeam (was: )
> CSS for test results panel/dock design
> --------------------------------------
>
> Key: DROOLS-2707
> URL: https://issues.jboss.org/browse/DROOLS-2707
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png
>
>
> As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules.
> *Verification conditions:*
> - CSS styles that employ relevant PatternFly styles and/or patterns.
> - CSS that articulates the design wireframe.
> - Reviewed by scrum team prior to PR/dev delivery.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2707:
--------------------------------
Description:
As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules.
*Verification conditions:*
- CSS styles that employ relevant PatternFly styles and/or patterns.
- CSS that articulates the design wireframe.
- Reviewed by scrum team prior to PR/dev delivery.
was:As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules.
> CSS for test results panel/dock design
> --------------------------------------
>
> Key: DROOLS-2707
> URL: https://issues.jboss.org/browse/DROOLS-2707
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png
>
>
> As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules.
> *Verification conditions:*
> - CSS styles that employ relevant PatternFly styles and/or patterns.
> - CSS that articulates the design wireframe.
> - Reviewed by scrum team prior to PR/dev delivery.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2707) Ability to review simulation test results
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-2707:
-----------------------------------
Summary: Ability to review simulation test results
Key: DROOLS-2707
URL: https://issues.jboss.org/browse/DROOLS-2707
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Liz Clayton
Assignee: Daniele Zonca
As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2706:
-------------------------------------
[~mstevens1] Thanks! [~Rikkola] [~stetson.robinson] [~ibek] Wdyt, could we use "Rules Scenario Test" and "Rules Scenario Test (Legacy)"?
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Matthew Stevens commented on DROOLS-2706:
-----------------------------------------
[~uxdlc] Business Process refers to the old designer as *Business Process (Legacy)* if that fits here.
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years