October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4619: -------------------------------------- Sprint: (was: 2019 Week 41-43 (from Okt 7)) > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4625: -------------------------------------- Sprint: 2019 Week 41-43 (from Okt 7) > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4631) Inserting already expired events are not taken into account in the collect operation in the first fireAllRules

by Oscar Molina (Jira)

Oscar Molina created DROOLS-4631: ------------------------------------ Summary: Inserting already expired events are not taken into account in the collect operation in the first fireAllRules Key: DROOLS-4631 URL: https://issues.jboss.org/browse/DROOLS-4631 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.27.0.Final Reporter: Oscar Molina Assignee: Mario Fusco Migrating a project from Drools 6.5.x to 7.x, if we insert already expired events, they are not taken into account in the collect operation in the first fireAllRules. Expired event in STREAM mode are not taken into account when using collect operation. it seems not to be aligned with drools design requirement: "Expired events does not cancel rule activations". This was not the case with the last 6.5 version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4630) Inserting already expired events are not taken into account in the collect operation in the first fireAllRules

by Oscar Molina (Jira)

Oscar Molina created DROOLS-4630: ------------------------------------ Summary: Inserting already expired events are not taken into account in the collect operation in the first fireAllRules Key: DROOLS-4630 URL: https://issues.jboss.org/browse/DROOLS-4630 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.27.0.Final Reporter: Oscar Molina Assignee: Mario Fusco Migrating a project from Drools 6.5.x to 7.x, if we insert already expired events, they are not taken into account in the collect operation in the first fireAllRules. Expired event in STREAM mode are not taken into account when using collect operation. it seems not to be aligned with drools design requirement: "Expired events does not cancel rule activations". This was not the case with the last 6.5 version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4630) Inserting already expired events are not taken into account in the collect operation in the first fireAllRules

by Oscar Molina (Jira)

[ https://issues.jboss.org/browse/DROOLS-4630?page=com.atlassian.jira.plugi... ] Oscar Molina deleted DROOLS-4630: --------------------------------- > Inserting already expired events are not taken into account in the collect operation in the first fireAllRules > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4630 > URL: https://issues.jboss.org/browse/DROOLS-4630 > Project: Drools > Issue Type: Bug > Reporter: Oscar Molina > Assignee: Mario Fusco > Priority: Major > Labels: support > > Migrating a project from Drools 6.5.x to 7.x, if we insert already expired events, they are not taken into account in the collect operation in the first fireAllRules. Expired event in STREAM mode are not taken into account when using collect operation. it seems not to be aligned with drools design requirement: "Expired events does not cancel rule activations". This was not the case with the last 6.5 version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4626) Inserting already expired events are not taken into account in the collect operation in the first fireAllRules

by Oscar Molina (Jira)

[ https://issues.jboss.org/browse/DROOLS-4626?page=com.atlassian.jira.plugi... ] Oscar Molina commented on DROOLS-4626: -------------------------------------- Note: This works in 7.2.0.Final and failed from 7.3.0.Final > Inserting already expired events are not taken into account in the collect operation in the first fireAllRules > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4626 > URL: https://issues.jboss.org/browse/DROOLS-4626 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.27.0.Final > Reporter: Oscar Molina > Assignee: Mario Fusco > Priority: Major > Labels: support > > Migrating a project from Drools 6.5.x to 7.x, if we insert already expired events, they are not taken into account in the collect operation in the first fireAllRules. Expired event in STREAM mode are not taken into account when using collect operation. it seems not to be aligned with drools design requirement: "Expired events does not cancel rule activations". This was not the case with the last 6.5 version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4626) Inserting already expired events are not taken into account in the collect operation in the first fireAllRules

by Oscar Molina (Jira)

[ https://issues.jboss.org/browse/DROOLS-4626?page=com.atlassian.jira.plugi... ] Oscar Molina updated DROOLS-4626: --------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2575 > Inserting already expired events are not taken into account in the collect operation in the first fireAllRules > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4626 > URL: https://issues.jboss.org/browse/DROOLS-4626 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.27.0.Final > Reporter: Oscar Molina > Assignee: Mario Fusco > Priority: Major > Labels: support > > Migrating a project from Drools 6.5.x to 7.x, if we insert already expired events, they are not taken into account in the collect operation in the first fireAllRules. Expired event in STREAM mode are not taken into account when using collect operation. it seems not to be aligned with drools design requirement: "Expired events does not cancel rule activations". This was not the case with the last 6.5 version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-971) Checker script is not checking istio pods correctly

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-971?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-971. --------------------------------- Resolution: Done > Checker script is not checking istio pods correctly > --------------------------------------------------- > > Key: SWSQE-971 > URL: https://issues.jboss.org/browse/SWSQE-971 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Sometimes it just checks that 2 pods are running and continuing not waiting for all pods to be up: > Validating that Istio status in namespace "istio-system" > Verifying that "istio-system" namespace exists... > Istio "istio-system" namespace exists. > Now using project "istio-system" on server "https://api.ocp4-kqe-auto1.maistra.upshift.redhat.com:6443". > Verifying status of istio_installer pod in namespace "istio-system".. > Installer pod does not exist. > Varifying status of istio pods in namespace "istio-system".. > Pod: istio-citadel-77bbdd86d7-twvfc Status: ContainerCreating > Waiting for all pods to be in Running status.. > Pod: istio-citadel-77bbdd86d7-twvfc Status: Running > Pod: prometheus-76596b5c54-65cwq Status: ContainerCreating > Waiting for all pods to be in Running status.. > Pod: istio-citadel-77bbdd86d7-twvfc Status: Running > Pod: prometheus-76596b5c54-65cwq Status: ContainerCreating > Waiting for all pods to be in Running status.. > Pod: istio-citadel-77bbdd86d7-twvfc Status: Running > Pod: prometheus-76596b5c54-65cwq Status: Running > All Istio pods are in Running status.. Istio is deployed successfully.. > Validating that Kialki is up in namespace "istio-system" > Verifying that Kiali pod is running and Kiali is browsable in namespace "istio-system".. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-972) Install maistra job fails because of existing resources for registry puller

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-972?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-972. --------------------------------- Resolution: Done > Install maistra job fails because of existing resources for registry puller > --------------------------------------------------------------------------- > > Key: SWSQE-972 > URL: https://issues.jboss.org/browse/SWSQE-972 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Error from server (AlreadyExists): error when creating "src/****files/templates/olm/custom/registryPuller.yaml": clusterroles.rbac.authorization.k8s.io "registry-puller" already exists > Error from server (AlreadyExists): error when creating "src/****files/templates/olm/custom/registryPuller.yaml": clusterrolebindings.rbac.authorization.k8s.io "registry-puller" already -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-972) Install maistra job fails because of existing resources for registry puller

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-972?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-972: ------------------------------------- https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/... > Install maistra job fails because of existing resources for registry puller > --------------------------------------------------------------------------- > > Key: SWSQE-972 > URL: https://issues.jboss.org/browse/SWSQE-972 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Error from server (AlreadyExists): error when creating "src/****files/templates/olm/custom/registryPuller.yaml": clusterroles.rbac.authorization.k8s.io "registry-puller" already exists > Error from server (AlreadyExists): error when creating "src/****files/templates/olm/custom/registryPuller.yaml": clusterrolebindings.rbac.authorization.k8s.io "registry-puller" already -- 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