October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3147) [DMN Designer] Keyboard shortcuts

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3147?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3147: -------------------------------- Epic Name: [DMN Designer] Keyboard shortcuts (was: BAPL-968 [DMN Designer] Keyboard shortcuts) > [DMN Designer] Keyboard shortcuts > --------------------------------- > > Key: DROOLS-3147 > URL: https://issues.jboss.org/browse/DROOLS-3147 > Project: Drools > Issue Type: Epic > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools, reported-by-qe > > The DMN editor should support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. This support is crucial for integration selenium testing. > In integration test we are able to select node on canvas thanks to Navigation Dock (BAPL-966). Once element is selected we need shortcuts for: > - Appending element > - Morphing element > - Renaming element > Thanks to Navigation Dock (BAPL-966) we are also able to open Context Editor (where applicable). In Context editor we need shortcuts for: > - Navigation between cells > - Invoking inline context menu > - Navigate in inline context menu > - Select item in inline context menu > - Start Editing cell > - Finish editing Cell > - Cancel editing Cell -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3147) [DMN Designer] Keyboard shortcuts

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3147?page=com.atlassian.jira.plugi... ] Jozef Marko moved BAPL-1089 to DROOLS-3147: ------------------------------------------- Project: Drools (was: Business Automation Planning) Key: DROOLS-3147 (was: BAPL-1089) Issue Type: Epic (was: Requirement) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Epic Name: BAPL-968 [DMN Designer] Keyboard shortcuts Epic Status: To Do QE Status: NEW > [DMN Designer] Keyboard shortcuts > --------------------------------- > > Key: DROOLS-3147 > URL: https://issues.jboss.org/browse/DROOLS-3147 > Project: Drools > Issue Type: Epic > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools, reported-by-qe > > The DMN editor should support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. This support is crucial for integration selenium testing. > In integration test we are able to select node on canvas thanks to Navigation Dock (BAPL-966). Once element is selected we need shortcuts for: > - Appending element > - Morphing element > - Renaming element > Thanks to Navigation Dock (BAPL-966) we are also able to open Context Editor (where applicable). In Context editor we need shortcuts for: > - Navigation between cells > - Invoking inline context menu > - Navigate in inline context menu > - Select item in inline context menu > - Start Editing cell > - Finish editing Cell > - Cancel editing Cell -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2947) [DMN Designer] change to structure data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2947?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2947. ------------------------------- Fix Version/s: 7.13.0.Final Resolution: Cannot Reproduce > [DMN Designer] change to structure data type is not stored > ---------------------------------------------------------- > > Key: DROOLS-2947 > URL: https://issues.jboss.org/browse/DROOLS-2947 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Fix For: 7.13.0.Final > > Attachments: Port Clearance Rules - Solution 3.dmn > > > If user changes some item in *Manage Custom Data Types* to *Structure* this change is not stored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3137: -------------------------------- Description: - When the "Add Constraints" check box is selected, the Constraints component must be loaded; - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). - Change of constraint type should re-render constraint component appropriately - Constraint component should be rendered appropriately between two openings of Manage Types dialog - Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console was: - When the "Add Constraints" check box is selected, the Constraints component must be loaded; - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). - Change of constraint type should re-render constraint component appropriately - Constraint component should be rendered appropriately between two openings of Manage Types dialog > [DMN Designer] Data Types Type - Constraints - MVP component > ------------------------------------------------------------ > > Key: DROOLS-3137 > URL: https://issues.jboss.org/browse/DROOLS-3137 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > - When the "Add Constraints" check box is selected, the Constraints component must be loaded; > - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; > - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); > - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); > - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). > - Change of constraint type should re-render constraint component appropriately > - Constraint component should be rendered appropriately between two openings of Manage Types dialog > - Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3137: -------------------------------- Description: - When the "Add Constraints" check box is selected, the Constraints component must be loaded; - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). - Change of constraint type should re-render constraint component appropriately - Constraint component should be rendered appropriately between two openings of Manage Types dialog was: - When the "Add Constraints" check box is selected, the Constraints component must be loaded; - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). > [DMN Designer] Data Types Type - Constraints - MVP component > ------------------------------------------------------------ > > Key: DROOLS-3137 > URL: https://issues.jboss.org/browse/DROOLS-3137 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > - When the "Add Constraints" check box is selected, the Constraints component must be loaded; > - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; > - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); > - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); > - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). > - Change of constraint type should re-render constraint component appropriately > - Constraint component should be rendered appropriately between two openings of Manage Types dialog -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3137: -------------------------------- Tester: Jozef Marko > [DMN Designer] Data Types Type - Constraints - MVP component > ------------------------------------------------------------ > > Key: DROOLS-3137 > URL: https://issues.jboss.org/browse/DROOLS-3137 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > - When the "Add Constraints" check box is selected, the Constraints component must be loaded; > - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component; > - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save); > - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save); > - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save). > - Change of constraint type should re-render constraint component appropriately > - Constraint component should be rendered appropriately between two openings of Manage Types dialog -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3116) [DMN Designer] Literal Expression is not saved

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3116?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3116: ---------------------------------------- Done as requested, with https://github.com/kiegroup/kie-wb-common/commit/ba5aefec948af9f1167f5501... > [DMN Designer] Literal Expression is not saved > ---------------------------------------------- > > Key: DROOLS-3116 > URL: https://issues.jboss.org/browse/DROOLS-3116 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Fix For: 7.13.0.Final > > > Literal Expression of decision node is not saved. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3146) [DMN Designer] Remove Context from Manage Data Type dialog

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3146: ----------------------------------- Summary: [DMN Designer] Remove Context from Manage Data Type dialog Key: DROOLS-3146 URL: https://issues.jboss.org/browse/DROOLS-3146 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.13.0.Final Reporter: Jozef Marko Assignee: Guilherme Carreiro We shouldn't offer *context* as an option in the *Manage Custom Data Types* dialog, however we should preserve this option for DRG nodes *Output data type* field. [~tirelli] could you please advise if we should keep *context* as an option for rows and columns in expression grid editor? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11188) Upgrade HAL to 3.0.7.Final

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11188?page=com.atlassian.jira.plugin... ] Harald Pehl closed WFLY-11188. ------------------------------ Fix Version/s: (was: 15.0.0.Alpha1) Resolution: Done Not relevant for upstream. For WildFly 15.x HAL 3.1.x will be used. > Upgrade HAL to 3.0.7.Final > -------------------------- > > Key: WFLY-11188 > URL: https://issues.jboss.org/browse/WFLY-11188 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Claudio Miranda > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) Scenario UX/Visual enhancements

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3126: ------------------------------------- Ok, here is my proposal lets collect UX tasks of _drools-tools_, _scenario-simulation_ and _stunner_ scrum teams and then identify cross-team UX epics. > Scenario UX/Visual enhancements > ------------------------------- > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > This item contains a list of general dev bugs, related to the UI. Team feedback is as follows, might require UX stories. > *Table/grid styling*: > (related DMN jira) > * Consider using grey borders for all the grid and not only for the header (team feedback) - refer to visual design on related DMN table first. > * Consider adding some padding to the cells of the grid (team feedback) - refer to visual design on related DMN table first. > * Reduce the width of Index column > *Docks/panels* > * Add some padding to right panel the tab titles > * Remove scrolling bar from right panel - relates to a known component issue. > _Scenario specific:_ > * Review expression editor component HTML/CSS (paddings, indents, etc) > * Review right panel padding (now it is hardcoded) > - Use text area inputs instead of text box for inline editing -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018