November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4686) Update documentation with version used in 7.5.1

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4686?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4686. ---------------------------------------- Resolution: Done > Update documentation with version used in 7.5.1 > ----------------------------------------------- > > Key: DROOLS-4686 > URL: https://issues.jboss.org/browse/DROOLS-4686 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4802) Fix topic partition check Hacep

by Jiri Petrlik (Jira)

[ https://issues.jboss.org/browse/DROOLS-4802?page=com.atlassian.jira.plugi... ] Jiri Petrlik commented on DROOLS-4802: -------------------------------------- [~mdessi] Can you be more specific here. What is this bug about? Is there any reproducer or test for this issue? > Fix topic partition check Hacep > ------------------------------- > > Key: DROOLS-4802 > URL: https://issues.jboss.org/browse/DROOLS-4802 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4801) Remove unused conf var form HACEP

by Jiri Petrlik (Jira)

[ https://issues.jboss.org/browse/DROOLS-4801?page=com.atlassian.jira.plugi... ] Jiri Petrlik commented on DROOLS-4801: -------------------------------------- [~mdessi] [~danielezonca] Wondering about priority here. Is issue about unused parameters really a blocker? Or is there some another problem caused by these variables? > Remove unused conf var form HACEP > --------------------------------- > > Key: DROOLS-4801 > URL: https://issues.jboss.org/browse/DROOLS-4801 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4724?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4724: -------------------------------- Description: Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. However Error message is reported anyway to the user: !image-2019-11-04-19-39-01-113.png|thumbnail! This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression !image-2019-11-04-19-40-27-201.png|thumbnail! so the current behavior is not consistent across re-open of the editor. Let's revert this default. The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). Currently, the DMN Compiler will throw 1 Warning. Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). Currently, the DMN Validator schema check is not reporting any XSD violation. h2. Manual acceptance test Try to save default / empty h3. Business Central - Decision node (?) - BKM node (?) - Cleared Function (?) - Context entry (?) [^error.log] [^save-context.webm] - Invocation (?) h3. Kogito - Decision node (?) - BKM node (?) - Cleared Function (?) - Context entry (?) - Invocation (?) was: Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. However Error message is reported anyway to the user: !image-2019-11-04-19-39-01-113.png|thumbnail! This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression !image-2019-11-04-19-40-27-201.png|thumbnail! so the current behavior is not consistent across re-open of the editor. Let's revert this default. The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). Currently, the DMN Compiler will throw 1 Warning. Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). Currently, the DMN Validator schema check is not reporting any XSD violation. h2. Manual acceptance test Try to save default / empty h3. Business Central - Decision node (/) - BKM node (/) - Cleared Function (/) - Context entry (x) [^error.log] [^save-context.webm] - Invocation (/) h3. Kogito - Decision node (/) - BKM node (/) - Cleared Function (/) - Context entry (/) - Invocation (/) > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.jboss.org/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node (?) > - BKM node (?) > - Cleared Function (?) > - Context entry (?) [^error.log] [^save-context.webm] > - Invocation (?) > h3. Kogito > - Decision node (?) > - BKM node (?) > - Cleared Function (?) > - Context entry (?) > - Invocation (?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4791) [DMN Designer] Not able to edit by double click after scroll

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4791?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4791: -------------------------------- Description: User is not able to invoke cell edito mode if he scrolled the dmn grid before. *Acceptance criteria* *_DMN_* - Import the attached file. - Follow general steps below. - Try to Drag and Drop Data type, Data Type Enumeration Constraint *_Guided Decision Table_* - Create/open existing asset. - Follow general steps below. *_Scenario Simulation_* - Create/open existing asset. - Follow general steps below. *_General steps_* (?) Double-click in cell to edit. (?) Press {{<Tab>}} keyboard operation should work. (?) Double-click in cell to edit. (?) Press {{<Escape>}} keyboard operation should work. (?) Click _elsewhere _ e.g. browser address bar. (?) Keyboard operation should not work (editor does not have focus) (?) Click on grid. (?) Keyboard operation should work. (?) Scroll the grid, Edit the cell, Keyboard Operation needs to work afterwards (?) Search the grid, Edit the cell, Keyboard Operation needs to work afterwards was: User is not able to invoke cell edito mode if he scrolled the dmn grid before. *Acceptance criteria* *_DMN_* - Import the attached file. - Follow general steps below. *_Guided Decision Table_* - Create/open existing asset. - Follow general steps below. *_Scenario Simulation_* - Create/open existing asset. - Follow general steps below. *_General steps_* (?) Double-click in cell to edit. (?) Press {{<Tab>}} keyboard operation should work. (?) Double-click in cell to edit. (?) Press {{<Escape>}} keyboard operation should work. (?) Click _elsewhere _ e.g. browser address bar. (?) Keyboard operation should not work (editor does not have focus) (?) Click on grid. (?) Keyboard operation should work. (?) Scroll the grid, Edit the cell, Keyboard Operation needs to work afterwards (?) Search the grid, Edit the cell, Keyboard Operation needs to work afterwards > [DMN Designer] Not able to edit by double click after scroll > ------------------------------------------------------------ > > Key: DROOLS-4791 > URL: https://issues.jboss.org/browse/DROOLS-4791 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: aTable.dmn, edit-cell.webm > > > User is not able to invoke cell edito mode if he scrolled the dmn grid before. > *Acceptance criteria* > *_DMN_* > - Import the attached file. > - Follow general steps below. > - Try to Drag and Drop Data type, Data Type Enumeration Constraint > *_Guided Decision Table_* > - Create/open existing asset. > - Follow general steps below. > *_Scenario Simulation_* > - Create/open existing asset. > - Follow general steps below. > *_General steps_* > (?) Double-click in cell to edit. > (?) Press {{<Tab>}} keyboard operation should work. > (?) Double-click in cell to edit. > (?) Press {{<Escape>}} keyboard operation should work. > (?) Click _elsewhere _ e.g. browser address bar. > (?) Keyboard operation should not work (editor does not have focus) > (?) Click on grid. > (?) Keyboard operation should work. > (?) Scroll the grid, Edit the cell, Keyboard Operation needs to work afterwards > (?) Search the grid, Edit the cell, Keyboard Operation needs to work afterwards -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2410) TestNG: upgrade to 7.0.0

by Bela Ban (Jira)

Bela Ban created JGRP-2410: ------------------------------ Summary: TestNG: upgrade to 7.0.0 Key: JGRP-2410 URL: https://issues.jboss.org/browse/JGRP-2410 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1.9 There were some issues running the stack-dependent tests in 7.0.0, that's why I reverted to 6.14.3. Need to revisit this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4791) [DMN Designer] Not able to edit by double click after scroll

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4791?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4791: -------------------------------- Description: User is not able to invoke cell edito mode if he scrolled the dmn grid before. *Acceptance criteria* *_DMN_* - Import the attached file. - Follow general steps below. *_Guided Decision Table_* - Create/open existing asset. - Follow general steps below. *_Scenario Simulation_* - Create/open existing asset. - Follow general steps below. *_General steps_* (?) Double-click in cell to edit. (?) Press {{<Tab>}} keyboard operation should work. (?) Double-click in cell to edit. (?) Press {{<Escape>}} keyboard operation should work. (?) Click _elsewhere _ e.g. browser address bar. (?) Keyboard operation should not work (editor does not have focus) (?) Click on grid. (?) Keyboard operation should work. (?) Scroll the grid, Edit the cell, Keyboard Operation needs to work afterwards (?) Search the grid, Edit the cell, Keyboard Operation needs to work afterwards was: User is not able to invoke cell edito mode if he scrolled the dmn grid before. *Acceptance criteria* *_DMN_* - Import the attached file. - Follow general steps below. *_Guided Decision Table_* - Create/open existing asset. - Follow general steps below. *_Scenario Simulation_* - Create/open existing asset. - Follow general steps below. *_General steps_* (?) Double-click in cell to edit. (?) Press {{<Tab>}} keyboard operation should work. (?) Double-click in cell to edit. (?) Press {{<Escape>}} keyboard operation should work. (?) Click _elsewhere _ e.g. browser address bar. (?) Keyboard operation should not work (editor does not have focus) (?) Click on grid. (?) Keyboard operation should work. > [DMN Designer] Not able to edit by double click after scroll > ------------------------------------------------------------ > > Key: DROOLS-4791 > URL: https://issues.jboss.org/browse/DROOLS-4791 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: aTable.dmn, edit-cell.webm > > > User is not able to invoke cell edito mode if he scrolled the dmn grid before. > *Acceptance criteria* > *_DMN_* > - Import the attached file. > - Follow general steps below. > *_Guided Decision Table_* > - Create/open existing asset. > - Follow general steps below. > *_Scenario Simulation_* > - Create/open existing asset. > - Follow general steps below. > *_General steps_* > (?) Double-click in cell to edit. > (?) Press {{<Tab>}} keyboard operation should work. > (?) Double-click in cell to edit. > (?) Press {{<Escape>}} keyboard operation should work. > (?) Click _elsewhere _ e.g. browser address bar. > (?) Keyboard operation should not work (editor does not have focus) > (?) Click on grid. > (?) Keyboard operation should work. > (?) Scroll the grid, Edit the cell, Keyboard Operation needs to work afterwards > (?) Search the grid, Edit the cell, Keyboard Operation needs to work afterwards -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4707) Update HACEP docs for Update kjar

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4707?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4707. ---------------------------------------- Release Notes Text: Replaced by https://issues.jboss.org/browse/DROOLS-4686 Resolution: Duplicate Issue > Update HACEP docs for Update kjar > --------------------------------- > > Key: DROOLS-4707 > URL: https://issues.jboss.org/browse/DROOLS-4707 > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1009) Service Details - DR Status Automate

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1009: ------------------------------------- Summary: Service Details - DR Status Automate Key: SWSQE-1009 URL: https://issues.jboss.org/browse/SWSQE-1009 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] User is unable to reorder structure items

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4803: ----------------------------------- Summary: [DMN Designer] User is unable to reorder structure items Key: DROOLS-4803 URL: https://issues.jboss.org/browse/DROOLS-4803 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.31.0.Final Reporter: Jozef Marko Assignee: karreiro Attachments: reorder-structure-items.webm If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 November 2019