December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1032) Create mailing list for service mesh qe

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1032?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1032. ---------------------------------- Resolution: Done https://post-office.corp.redhat.com/mailman/listinfo/service-mesh-qe > Create mailing list for service mesh qe > --------------------------------------- > > Key: SWSQE-1032 > URL: https://issues.redhat.com/browse/SWSQE-1032 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4665) Scenario Background toolbar buttons state

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4665?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4665: -------------------------------- Sprint: (was: 2019 Week 50-52 (from Dec 9)) > Scenario Background toolbar buttons state > ----------------------------------------- > > Key: DROOLS-4665 > URL: https://issues.redhat.com/browse/DROOLS-4665 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Fix For: 7.32.0.Final > > > The Scenario Background tab disable some toolbar buttons, however they stay disabled depending on the order of selecting editor tabs. See the [comment|https://github.com/kiegroup/drools-wb/pull/1239#discussion_r33636...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4665) Scenario Background toolbar buttons state

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4665?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4665. ------------------------------- Fix Version/s: 7.32.0.Final Resolution: Cannot Reproduce [~yamer] thank you, I can confirm. > Scenario Background toolbar buttons state > ----------------------------------------- > > Key: DROOLS-4665 > URL: https://issues.redhat.com/browse/DROOLS-4665 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Fix For: 7.32.0.Final > > > The Scenario Background tab disable some toolbar buttons, however they stay disabled depending on the order of selecting editor tabs. See the [comment|https://github.com/kiegroup/drools-wb/pull/1239#discussion_r33636...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4664) Scenario Background Table row duplication

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4664?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4664: -------------------------------- Sprint: (was: 2019 Week 50-52 (from Dec 9)) > Scenario Background Table row duplication > ----------------------------------------- > > Key: DROOLS-4664 > URL: https://issues.redhat.com/browse/DROOLS-4664 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Fix For: 7.32.0.Final > > > Currently the Scenario Background table row duplication doesn't work, 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, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4664) Scenario Background Table row duplication

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4664?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4664. ------------------------------- Fix Version/s: 7.32.0.Final Resolution: Cannot Reproduce [~yamer] yes, I can confirm, thank you. > Scenario Background Table row duplication > ----------------------------------------- > > Key: DROOLS-4664 > URL: https://issues.redhat.com/browse/DROOLS-4664 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Fix For: 7.32.0.Final > > > Currently the Scenario Background table row duplication doesn't work, 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, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4383) DMN DT exec model does not cascade down allowedValues to input/outputValues of DT

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4383?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-4383: ------------------------------------------- Matteo mentioned: {noformat} I would leave aside https://issues.redhat.com/browse/DROOLS-4383, as more recent decisions will possibly make that work non necessary, at that part of the code as a whole will likely be substituted by another implementation. {noformat} > DMN DT exec model does not cascade down allowedValues to input/outputValues of DT > --------------------------------------------------------------------------------- > > Key: DROOLS-4383 > URL: https://issues.redhat.com/browse/DROOLS-4383 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > See [DROOLS-4379] test case a. To be investigated: there is a slight diff behavior when using interpreted Vs exec-model, as the allowedValues does not seems to be cascaded down from the ItemDefinition to the input/outputValues of the Decision Table -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4383) DMN DT exec model does not cascade down allowedValues to input/outputValues of DT

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4383?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4383: -------------------------------------- Labels: (was: good-first-issue) > DMN DT exec model does not cascade down allowedValues to input/outputValues of DT > --------------------------------------------------------------------------------- > > Key: DROOLS-4383 > URL: https://issues.redhat.com/browse/DROOLS-4383 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > See [DROOLS-4379] test case a. To be investigated: there is a slight diff behavior when using interpreted Vs exec-model, as the allowedValues does not seems to be cascaded down from the ItemDefinition to the input/outputValues of the Decision Table -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1032) Create mailing list for service mesh qe

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1032?page=com.atlassian.jira.plugi... ] Filip Brychta commented on SWSQE-1032: -------------------------------------- Created https://redhat.service-now.com/surl.do?n=RITM0590468 > Create mailing list for service mesh qe > --------------------------------------- > > Key: SWSQE-1032 > URL: https://issues.redhat.com/browse/SWSQE-1032 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4799) Adding "expression" type handling for Collection type propereties

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Jozef Marko edited comment on DROOLS-4799 at 12/10/19 2:14 AM: --------------------------------------------------------------- [~uxdlc] ok I will try to explain my thoughts. In dmn data type constraints, user can define the same constraint using both "Enumeration" and "Expression" editor. In other words, the defined constraint doesn't need to be dropped during switching between editors because both have the same expressing power. In the two pictures below the constraint is defined: - !dmn-dt-enumeration-constraint.png|thumbnail! - !dmn-dt-expression-constraint.png|thumbnail! So my idea is when user define scesim list like (I guess is create list option in your wireframes): !scesim-list.png|thumbnail! Then switching to define list option could show a value {{Arrays.asList("green", "blue")}} or something. I am sure it would be doable for simple lists (string, numbers ...) Not sure about lists of custom objects, developers need to advise. was (Author: jomarko): [~uxdlc] ok I will try to explain my thoughts. In dmn data type constraints, user can define the same constraint using both "Enumeration" and "Expression" editor. In other words, the defined constraint doesn't need to be dropped during switching between editors because both have the same expressing power. In the two pictures below the constraint is defined: - !dmn-dt-enumeration-constraint.png|thumbnail! - !dmn-dt-expression-constraint.png|thumbnail! So my idea is when user define scesim list like (I guess is create list option in your wireframes): !expression-list_error.png|thumbnail! Then switching to define list option could show a value {{Arrays.asList("green", "blue")}} or something. I am sure it would be doable for simple lists (string, numbers ...) Not sure about lists of custom objects, developers need to advise. > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.redhat.com/browse/DROOLS-4799 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png, expression-list_error.png, scesim-list.png > > > I need a clarification regarding the behaviour of the updated Collection Editor, in particular for this section -->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330. > Considering the editor introduces a new way to handle a Collection ("Define List"), can you please give us detailed behaviour for the following case: > - What happen if a user starts to input data inside a section (Define List/Create List) and then switch on the other one? > eg. if I start to define a List using "Define List" option (i.e. an expression) and then I change to "Create List" case. What should happen? > - Currently, after adding a Collection, the Grid cell will show "List (1)". It should be the same for "Define list" (i.e. Expression) case? > In case of additional clarificaiton, I'll update this ticket. > Hope it's clear, if not you can contact me anytime. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4799) Adding "expression" type handling for Collection type propereties

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4799: ------------------------------------- [~uxdlc] ok I will try to explain my thoughts. In dmn data type constraints, user can define the same constraint using both "Enumeration" and "Expression" editor. In other words, the defined constraint doesn't need to be dropped during switching between editors because both have the same expressing power. In the two pictures below the constraint is defined: - !dmn-dt-enumeration-constraint.png|thumbnail! - !dmn-dt-expression-constraint.png|thumbnail! So my idea is when user define scesim list like (I guess is create list option in your wireframes): !expression-list_error.png|thumbnail! Then switching to define list option could show a value {{Arrays.asList("green", "blue")}} or something. I am sure it would be doable for simple lists (string, numbers ...) Not sure about lists of custom objects, developers need to advise. > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.redhat.com/browse/DROOLS-4799 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png, expression-list_error.png, scesim-list.png > > > I need a clarification regarding the behaviour of the updated Collection Editor, in particular for this section -->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330. > Considering the editor introduces a new way to handle a Collection ("Define List"), can you please give us detailed behaviour for the following case: > - What happen if a user starts to input data inside a section (Define List/Create List) and then switch on the other one? > eg. if I start to define a List using "Define List" option (i.e. an expression) and then I change to "Create List" case. What should happen? > - Currently, after adding a Collection, the Grid cell will show "List (1)". It should be the same for "Define list" (i.e. Expression) case? > In case of additional clarificaiton, I'll update this ticket. > Hope it's clear, if not you can contact me anytime. > Thanks -- 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 December 2019