[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3879:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> Create Kogito version of Test Scenarios designer
> ------------------------------------------------
>
> Key: DROOLS-3879
> URL: https://issues.jboss.org/browse/DROOLS-3879
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Create the *Kogito* versions of scesim editor.
> No Home Page, no Library, No preferences, no other editors.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4102) Persist/reload Test Scenario table width/height
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4102?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4102:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 23-25, 2019 Week 29-31)
> Persist/reload Test Scenario table width/height
> -----------------------------------------------
>
> Key: DROOLS-4102
> URL: https://issues.jboss.org/browse/DROOLS-4102
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: screencast-01-08-19-1.webm, screencast-02-08-19-1.webm
>
>
> Implement a mechanism to store/restore column width ({{FactMapping}}) and row height ({{Scenario}}) for the table in Test Scenario.
> Please consider:
> - Create/save a simulation (default column width/row height in scesim)
> - Rename a simulation (it perform a save/reload)
> - Change column type (recreate the column)
> - Duplicate column (preserve same size)
> - -Duplicate row (preserve same size)-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4061) Guided Score card rules not executed via test scenario.
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4061?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4061:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> Guided Score card rules not executed via test scenario.
> -------------------------------------------------------
>
> Key: DROOLS-4061
> URL: https://issues.jboss.org/browse/DROOLS-4061
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Reporter: Abhijit Humbe
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, support
> Attachments: MySpace_test-gscore.zip, Screenshot from 2019-06-26 10-13-47.png
>
>
> Test scenario is not executing rules from guided score card in RHPAM 7.3 GA release . I can see similar issue with both test scenario(new and legacy)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3954) DM UX solutions for communicating errors in graphs & grids.
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3954?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3954:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> DM UX solutions for communicating errors in graphs & grids.
> ------------------------------------------------------------
>
> Key: DROOLS-3954
> URL: https://issues.jboss.org/browse/DROOLS-3954
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Margot Menestrot
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Current DM context specific "design pattern" document: https://docs.google.com/document/d/1fX9K_fDjEO4_wDLK9EDDb0OtEFir7S6nFH9cn...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3957?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3957:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> Make verifier panel use docks
> -----------------------------
>
> Key: DROOLS-3957
> URL: https://issues.jboss.org/browse/DROOLS-3957
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: v&v.webm
>
>
> Pretty sure we had a ticket for this, but could not find it. Here it is.
> h3. Acceptance test
> On both Firefox and Chrome (x)
> - Opening multiple decision tables, switching between them
> - Repeated reopening of guided decision table
> - Opening other asset that uses docks - scenario, data object
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4245:
-----------------------------------
Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 26-28, 2019 Week 29-31)
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: RedHat_KIE_logo.eps, RedHat_KIE_logo.png, RedHat_KIE_logo.svg, doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3953:
-----------------------------------
Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 26-28, 2019 Week 29-31)
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Margot Menestrot
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4270:
-----------------------------------
Sprint: 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 29-31)
> Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
> -------------------------------------------------------------------
>
> Key: DROOLS-4270
> URL: https://issues.jboss.org/browse/DROOLS-4270
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, guided-decision-table-find.gif
>
>
> As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area.
> Find is a local search that could be performed in these areas of the application:
> * Guided Decision Table editor (tables) - text strings within "Data cells"
> * DMN graph- text strings within canvas nodes.
> * DMN boxed expressions (logic) - text strings within "Data cells"
> Requirements
> * Colors, etc for partial and whole text strings will need to be highlighted is required.
> * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes.
> * Visual styles for the above if recommended.
> Considerations
> * Will not be able to leverage browser controls for Find.
> * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4315) [DMN Designer] Documentation - Download buttons UX
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4315?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4315:
-----------------------------------
Sprint: 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 29-31)
> [DMN Designer] Documentation - Download buttons UX
> --------------------------------------------------
>
> Key: DROOLS-4315
> URL: https://issues.jboss.org/browse/DROOLS-4315
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Margot Menestrot
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months