October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4484: -------------------------------- Attachment: issue3-click-hide.webm > [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism > ----------------------------------------------------------------------------------------- > > Key: DROOLS-4484 > URL: https://issues.jboss.org/browse/DROOLS-4484 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: issue1-drag-edit.webm, issue3-click-hide.webm, s1.gif, s2.gif, s3.gif, s4.gif, s5.gif > > > This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. > *Acceptance criteria:* > - The drag and drop feature must behaves as the following scenarios describe: > -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: > !s1.gif|width=400! > -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: > !s2.gif|width=400! > -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: > !s3.gif|width=400! > -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: > !s4.gif|width=400! > -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: > !s5.gif|width=400! > - The keyboard control can not be affected > -- User need to be able start edit mode > -- User need to be able finish/cancel edit mode > - Search can not be affected > - Imported data types are not editable -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4484: -------------------------------- Description: This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. *Acceptance criteria:* - The drag and drop feature must behaves as the following scenarios describe: -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: !s1.gif|width=400! -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: !s2.gif|width=400! -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: !s3.gif|width=400! -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: !s4.gif|width=400! -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: !s5.gif|width=400! - The keyboard control can not be affected -- User need to be able start edit mode -- User need to be able finish/cancel edit mode - Search can not be affected - Imported data types are not editable was: This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. *Acceptance criteria:* - The drag and drop feature must behaves as the following scenarios describe: -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: !s1.gif|width=400! -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: !s2.gif|width=400! -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: !s3.gif|width=400! -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: !s4.gif|width=400! -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: !s5.gif|width=400! - The keyboard control can not be affected -- User need to be able start edit mode -- User need to be able finish/cancel edit mode - Search can not be affected > [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism > ----------------------------------------------------------------------------------------- > > Key: DROOLS-4484 > URL: https://issues.jboss.org/browse/DROOLS-4484 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: issue1-drag-edit.webm, s1.gif, s2.gif, s3.gif, s4.gif, s5.gif > > > This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. > *Acceptance criteria:* > - The drag and drop feature must behaves as the following scenarios describe: > -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: > !s1.gif|width=400! > -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: > !s2.gif|width=400! > -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: > !s3.gif|width=400! > -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: > !s4.gif|width=400! > -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: > !s5.gif|width=400! > - The keyboard control can not be affected > -- User need to be able start edit mode > -- User need to be able finish/cancel edit mode > - Search can not be affected > - Imported data types are not editable -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4674) Temporary remove background Tab

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4674?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4674: ------------------------------- Component/s: Scenario Simulation and Testing > Temporary remove background Tab > ------------------------------- > > Key: DROOLS-4674 > URL: https://issues.jboss.org/browse/DROOLS-4674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulationTeam > Fix For: 7.29.0.Final > > > Temporary remove Background Grid tab for 7.29.0 release, considering it is not ready to be used by users -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4674) Temporary remove background Tab

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4674?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4674: ------------------------------- Labels: ScenarioSimulationTeam (was: ) > Temporary remove background Tab > ------------------------------- > > Key: DROOLS-4674 > URL: https://issues.jboss.org/browse/DROOLS-4674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulationTeam > Fix For: 7.29.0.Final > > > Temporary remove Background Grid tab for 7.29.0 release, considering it is not ready to be used by users -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4541) Refactorting code to support a background grid in ScenarioSimulation

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4541?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4541: ------------------------------- Fix Version/s: (was: 7.6.0.Final) > Refactorting code to support a background grid in ScenarioSimulation > -------------------------------------------------------------------- > > Key: DROOLS-4541 > URL: https://issues.jboss.org/browse/DROOLS-4541 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4647) Update History (undo & redo actions) to support Background grid

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4647?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4647: ------------------------------- Fix Version/s: (was: 7.6.0.Final) > Update History (undo & redo actions) to support Background grid > --------------------------------------------------------------- > > Key: DROOLS-4647 > URL: https://issues.jboss.org/browse/DROOLS-4647 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Attachments: undo.webm > > > The current incorrect behavior of undo for background tabs is shown in the video [^undo.webm] > h2. Acceptance criteria > The undo/redo action should be taken on the correct tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4648) Define and Implement a DataModel to hold Background Table Data

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4648?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4648: ------------------------------- Fix Version/s: (was: 7.6.0.Final) > Define and Implement a DataModel to hold Background Table Data > -------------------------------------------------------------- > > Key: DROOLS-4648 > URL: https://issues.jboss.org/browse/DROOLS-4648 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Gabriele Cardosi > Priority: Major > Attachments: background-prova > > > This Feature is needed because currently after reopening the test scenario file, the background tab is populated with data from the model tab. For more details see the [comment|https://github.com/kiegroup/drools-wb/pull/1239#issuecomment-5436...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4643) Make configurable Kafka's consumers poll time

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4643?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4643. ---------------------------------------- Resolution: Done > Make configurable Kafka's consumers poll time > ---------------------------------------------- > > Key: DROOLS-4643 > URL: https://issues.jboss.org/browse/DROOLS-4643 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4484: -------------------------------- Description: This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. *Acceptance criteria:* - The drag and drop feature must behaves as the following scenarios describe: -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: !s1.gif|width=400! -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: !s2.gif|width=400! -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: !s3.gif|width=400! -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: !s4.gif|width=400! -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: !s5.gif|width=400! - The keyboard control can not be affected -- User need to be able start edit mode -- User need to be able finish/cancel edit mode - Search can not be affected was: This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. *Acceptance criteria:* - The drag and drop feature must behaves as the following scenarios describe: -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: !s1.gif|width=400! -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: !s2.gif|width=400! -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: !s3.gif|width=400! -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: !s4.gif|width=400! -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: !s5.gif|width=400! > [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism > ----------------------------------------------------------------------------------------- > > Key: DROOLS-4484 > URL: https://issues.jboss.org/browse/DROOLS-4484 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: issue1-drag-edit.webm, s1.gif, s2.gif, s3.gif, s4.gif, s5.gif > > > This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. > *Acceptance criteria:* > - The drag and drop feature must behaves as the following scenarios describe: > -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: > !s1.gif|width=400! > -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: > !s2.gif|width=400! > -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: > !s3.gif|width=400! > -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: > !s4.gif|width=400! > -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: > !s5.gif|width=400! > - The keyboard control can not be affected > -- User need to be able start edit mode > -- User need to be able finish/cancel edit mode > - Search can not be affected -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4484: -------------------------------- Attachment: issue1-drag-edit.webm > [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism > ----------------------------------------------------------------------------------------- > > Key: DROOLS-4484 > URL: https://issues.jboss.org/browse/DROOLS-4484 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: issue1-drag-edit.webm, s1.gif, s2.gif, s3.gif, s4.gif, s5.gif > > > This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. > *Acceptance criteria:* > - The drag and drop feature must behaves as the following scenarios describe: > -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: > !s1.gif|width=400! > -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: > !s2.gif|width=400! > -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: > !s3.gif|width=400! > -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: > !s4.gif|width=400! > -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: > !s5.gif|width=400! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2019