March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-3077 at 3/6/19 10:56 AM: ----------------------------------------------------------------- [~uxdlc] LGTM. [~tirelli] Could you please confirm/clarify. On https://redhat.invisionapp.com/share/DEQTMGIXU3Y#/screens/350182304 (where Age is the selected Data Type, with a Data Type constraint defined) it is clear that the _additional constraint_ will be on the {{InputClause}}'s {{UnaryTest}}. However on https://redhat.invisionapp.com/share/DEQTMGIXU3Y#/screens/350182306 (where the selected Data Type has no Data Type constraint defined) should the _additional constraint_ be added to the Data Type or the {{InputClause}}'s {{UnaryTest}} - I'd assume, for consistency, it'd be on the {{InputClause}}'s {{UnaryTest}} but want to be sure! was (Author: manstis): [~uxdlc] LGTM. [~tirelli] Could you please confirm/clarify. On https://redhat.invisionapp.com/share/DEQTMGIXU3Y#/screens/350182304 (where Age is the selected Data Type, with a Data Type constraint defined) it is clear that the _additional constraint_ will be on the {{InputClause}}'s {{UnaryTest}. However on https://redhat.invisionapp.com/share/DEQTMGIXU3Y#/screens/350182306 (where the selected Data Type has no Data Type constraint defined) should the _additional constraint_ be added to the Data Type or the {{InputClause}}'s {{UnaryTest}} - I'd assume, for consistency, it'd be on the {{InputClause}}'s {{UnaryTest}} but want to be sure! > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3077: --------------------------------------- Additional constraints should be added to the InputClause. > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2609) Implement decision table analysis as DMN validator extension

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-2609?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2609: ----------------------------------- Description: The scope of this JIRA will be > Implement decision table analysis as DMN validator extension > ------------------------------------------------------------ > > Key: DROOLS-2609 > URL: https://issues.jboss.org/browse/DROOLS-2609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Fedor Gavrilov > Assignee: Matteo Mortari > Priority: Major > Attachments: Algorithms for Decision Table Analysis.docx > > > The scope of this JIRA will be -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3683) [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3683?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3683: ---------------------------------------- You need to de-select the {{InputData}} by first selecting another node and then the {{InputData}} again. The "Properties Panel" content does not update when changes on the Data Type tab affects available data-types. > [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3683 > URL: https://issues.jboss.org/browse/DROOLS-3683 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Data Types are not refreshing the properties panel. > Steps to reproduce > - Add two input nodes ("Driver" and "Violation) > - Add two decision nodes ("Suspended?" and "Fine?") > - Connect "Drive" to "Suspended?" > - Connect "Violation" to "Fine?" > - Connect "Fine?" to "Suspended?" > - Select "Violation" > - Create three new DTs with an input node selected > - Go back to the graph > - Noticed the "Output data type" dropdown is not updated -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3683) [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3683?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-3683 at 3/6/19 9:30 AM: ---------------------------------------------------------------- You need to re-select the {{InputData}} by first selecting another node and then the {{InputData}} again. The "Properties Panel" content does not update when changes on the Data Type tab affects available data-types. was (Author: manstis): You need to de-select the {{InputData}} by first selecting another node and then the {{InputData}} again. The "Properties Panel" content does not update when changes on the Data Type tab affects available data-types. > [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3683 > URL: https://issues.jboss.org/browse/DROOLS-3683 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Data Types are not refreshing the properties panel. > Steps to reproduce > - Add two input nodes ("Driver" and "Violation) > - Add two decision nodes ("Suspended?" and "Fine?") > - Connect "Drive" to "Suspended?" > - Connect "Violation" to "Fine?" > - Connect "Fine?" to "Suspended?" > - Select "Violation" > - Create three new DTs with an input node selected > - Go back to the graph > - Noticed the "Output data type" dropdown is not updated -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-630) Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-630?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-630: ------------------------------- Summary: Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing (was: Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing) > Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing > ------------------------------------------------------------ > > Key: SWSQE-630 > URL: https://issues.jboss.org/browse/SWSQE-630 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Priority: Major > > There is a need to run soak tests on Kiali Beta and GA builds, that will run for about 5 days. This can not currently be done on OCP4/AWS due to the 48hr cluster life restriction. > As an alternative to OCP4/AWS, run the Kiali soak tests on Openshift 3.11, and so so in the PSI Openstack infrastructure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-630) Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-630: ---------------------------------- Summary: Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing Key: SWSQE-630 URL: https://issues.jboss.org/browse/SWSQE-630 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney There is a need to run soak tests on Kiali Beta and GA builds, that will run for about 5 days. This can not currently be done on OCP4/AWS due to the 48hr cluster life restriction. As an alternative to OCP4/AWS, run the Kiali soak tests on Openshift 3.11, and so so in the PSI Openstack infrastructure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-629) Set up monitoring for istio PSI OpenStack project

by Filip Brychta (Jira)

Filip Brychta created SWSQE-629: ----------------------------------- Summary: Set up monitoring for istio PSI OpenStack project Key: SWSQE-629 URL: https://issues.jboss.org/browse/SWSQE-629 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We want to monitor usage of the cluster and send emails with usage to users and alerts when we are coming close to the resource limits. Maybe send email warning for long running machines to owners? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-622) Create a Polarion Test Run TEmplate for Beta/GA

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-622?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-622. ---------------------------------- Resolution: Done https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > Create a Polarion Test Run TEmplate for Beta/GA > ----------------------------------------------- > > Key: SWSQE-622 > URL: https://issues.jboss.org/browse/SWSQE-622 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently we already have a template: https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > We need to add all important testcases into that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-155) WildFly gets stuck with TLSv1.3 on JDK 11

by Pavel Jelinek (Jira)

[ https://issues.jboss.org/browse/WFWIP-155?page=com.atlassian.jira.plugin.... ] Pavel Jelinek updated WFWIP-155: -------------------------------- Labels: jdk11 (was: ) > WildFly gets stuck with TLSv1.3 on JDK 11 > ----------------------------------------- > > Key: WFWIP-155 > URL: https://issues.jboss.org/browse/WFWIP-155 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Environment: JDK 11 > Reporter: Adam Krajcik > Assignee: Farah Juma > Priority: Blocker > Labels: jdk11 > > WildFly gets stuck with when using TLSv1.3. The process starts to heavily use the processor and cannot be stopped by simple SIGINT(Ctrl+C). The issue needs further investigation as no apparent reason for it being stuck. > One possibility is mentioned in the comments for UNDERTOW-1493 is [JDK-8208526|https://bugs.openjdk.java.net/browse/JDK-8208526]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019