December 2019 - jboss-jira - Jboss List Archives

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

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4799?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4799: ------------------------------------------- [~yamer] - Concerning 1) I'm wondering if a notification might be too disruptive/annoying? So I'm debating an alternative approach, which is to prevent them from switching once they've starting creating a list. To do that I was thinking we could disable the other radio button option, but allow it to be enabled if the user clears the form. Here's an example, wdyt? !expression-list_error.png|thumbnail! > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.jboss.org/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, expression-list_error.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 Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4799?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4799: -------------------------------------- Attachment: expression-list_error.png > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.jboss.org/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, expression-list_error.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] (SWSQE-1021) Verify View in Grafana link

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-1021?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan resolved SWSQE-1021. ----------------------------------- Resolution: Done > Verify View in Grafana link > --------------------------- > > Key: SWSQE-1021 > URL: https://issues.jboss.org/browse/SWSQE-1021 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1740) Clean up the 'wildfly-elytron-sasl' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1740?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1740: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-sasl' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1740 > URL: https://issues.jboss.org/browse/ELY-1740 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1739) Clean up the 'wildfly-elytron-jaspi' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1739?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1739: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-jaspi' module as it currently contains both public and private API > ------------------------------------------------------------------------------------------------ > > Key: ELY-1739 > URL: https://issues.jboss.org/browse/ELY-1739 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1737) Clean up the 'wildfly-elytron-credential-store' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1737?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1737: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-credential-store' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------------------- > > Key: ELY-1737 > URL: https://issues.jboss.org/browse/ELY-1737 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1735) Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1735?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1735: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1735 > URL: https://issues.jboss.org/browse/ELY-1735 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4, 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1725) Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1725?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1725: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ---------------------------------------------------------------------- > > Key: ELY-1725 > URL: https://issues.jboss.org/browse/ELY-1725 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha7 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1539) Remove deprecated AuthConf setHost, setProtocol, setPort properties

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1539?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1539: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Remove deprecated AuthConf setHost, setProtocol, setPort properties > ------------------------------------------------------------------- > > Key: ELY-1539 > URL: https://issues.jboss.org/browse/ELY-1539 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Priority: Critical > Fix For: 2.0.0.Alpha7 > > > We should deprecate (with a view towards removal) the setHost, setPort, and setProtocol properties of AuthenticationConfiguration. These properties are only sporadically utilized by backing systems, and often cause complex problems when they are used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1907) Release WildFly Elytron 2.0.0.Alpha6

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1907?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1907: ---------------------------- Fix Version/s: 2.0.0.Alpha7 (was: 2.0.0.Alpha6) > Release WildFly Elytron 2.0.0.Alpha6 > ------------------------------------ > > Key: ELY-1907 > URL: https://issues.jboss.org/browse/ELY-1907 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha7 > > -- 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