August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2919) [DMN Designer] Data-types: Clean-up

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2919?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2919: ----------------------------------- Description: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... (If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation) * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. was: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > [DMN Designer] Data-types: Clean-up > ----------------------------------- > > Key: DROOLS-2919 > URL: https://issues.jboss.org/browse/DROOLS-2919 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. > Current action items: > * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 > * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 > * https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... (If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation) > * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2919) [DMN Designer] Data-types: Clean-up

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2919?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2919: ----------------------------------- Description: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. was: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... (If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation) * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > [DMN Designer] Data-types: Clean-up > ----------------------------------- > > Key: DROOLS-2919 > URL: https://issues.jboss.org/browse/DROOLS-2919 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. > Current action items: > * https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 > * https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 > * https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. > * Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-2922 at 8/30/18 10:45 AM: --------------------------------------------------------------- Adding a pic with some callouts to sum my understanding of the agreements on the final design. The items with pink callouts are things that I assume can be added as elements even if it can't be styled immediately. The degree to which [~manstis] [~karreiro] you are able to style these to align with common PF or WB elements, I hope you and [~srambach] can discuss and align on that. The items with gold callouts, reflect my assumption around which elements rely specifically on CSS/Html styling provided through this jira. A) Form field labels for usability (context) and accessibility. B) Group the two actions (edit name, select data type) conceptually under a single task (Edit Decision) which is the pop-up title. C) Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. Note: Manage link opens the Manage dialog. D) Data type selector with "Live Search" type-ahead. Note: dropdown should expand within the pop-over. [~srambach] I believe that [~karreiro] has a solution for this dropdown. *E & F)* Use variant 1 of the PF pop-over patterns, which includes a title, pointer, and close icon. !pop-overcSpecs.png|thumbnail! was (Author: uxdlc): Adding a pic with some callouts to sum my understanding of the agreements on the final design. The items with pink callouts are things that I assume can be added as elements even if it can't be styled immediately. The degree to which [~manstis] [~karreiro] you are able to style these to align with common PF or WB elements, I hope you and [~srambach] can discuss and align on that. The items with gold ones, is my assumption around which elements rely specifically on CSS/Html styling provided through this jira. A) Form field labels for usability (context) and accessibility. B) Group the two actions (edit name, select data type) conceptually under a single task (Edit Decision) which is the pop-up title. C) Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. Note: Manage link opens the Manage dialog. D) Data type selector with "Live Search" type-ahead. Note: dropdown should expand within the pop-over. [~srambach] I believe that [~karreiro] has a solution for this dropdown. *E & F)* Use variant 1 of the PF pop-over patterns, which includes a title, pointer, and close icon. !pop-overcSpecs.png|thumbnail! > CSS: Pop-over menu for DMN decision tables. > ------------------------------------------- > > Key: DROOLS-2922 > URL: https://issues.jboss.org/browse/DROOLS-2922 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > 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, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases from the DMN canvas view, as a user I want to: > * Search a list of available data types from a decision table, as part of an input/selection process. > * Select a data type inline from a decision table. > * Have a means to rename the Decision (node.) > * Have a means to access the Manage Data Types dialog. > Notes: > Design requires a Pop-over, which includes: > * Form field labels for usability (context) and accessibility. > * Variant 1 of the PF pop-over patterns, which supports a the pop-up title. > * Drop down component with Live Search > * "Manage" link opens a dialog. > * Pop-up is initiated by a single-left mouse click within the respective decision table cell. > * Design needs to be reasonably consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4078) TimeZone is not correctly taken into account when checking certification expiration

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-4078: ----------------------------------------- Summary: TimeZone is not correctly taken into account when checking certification expiration Key: WFCORE-4078 URL: https://issues.jboss.org/browse/WFCORE-4078 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 6.0.1.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor When checking if a certificate should be renewed the"not After" date doesn't take the local timezone into account thus returning a possibly wrong value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2922: -------------------------------- Attachment: pop-overcSpecs.png > CSS: Pop-over menu for DMN decision tables. > ------------------------------------------- > > Key: DROOLS-2922 > URL: https://issues.jboss.org/browse/DROOLS-2922 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > 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, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases from the DMN canvas view, as a user I want to: > * Search a list of available data types from a decision table, as part of an input/selection process. > * Select a data type inline from a decision table. > * Have a means to rename the Decision (node.) > * Have a means to access the Manage Data Types dialog. > Notes: > Design requires a Pop-over, which includes: > * Form field labels for usability (context) and accessibility. > * Variant 1 of the PF pop-over patterns, which supports a the pop-up title. > * Drop down component with Live Search > * "Manage" link opens a dialog. > * Pop-up is initiated by a single-left mouse click within the respective decision table cell. > * Design needs to be reasonably consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2922: ------------------------------------- Adding a pic with some callouts to sum my understanding of the agreements on the final design. The items with pink callouts are things that I assume can be added as elements even if it can't be styled immediately. The degree to which [~manstis] [~karreiro] you are able to style these to align with common PF or WB elements, I hope you and [~srambach] can discuss and align on that. The items with gold ones, is my assumption around which elements rely specifically on CSS/Html styling provided through this jira. A) Form field labels for usability (context) and accessibility. B) Group the two actions (edit name, select data type) conceptually under a single task (Edit Decision) which is the pop-up title. C) Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. Note: Manage link opens the Manage dialog. D) Data type selector with "Live Search" type-ahead. Note: dropdown should expand within the pop-over. [~srambach] I believe that [~karreiro] has a solution for this dropdown. *E & F)* Use variant 1 of the PF pop-over patterns, which includes a title, pointer, and close icon. !pop-overcSpecs.png|thumbnail! > CSS: Pop-over menu for DMN decision tables. > ------------------------------------------- > > Key: DROOLS-2922 > URL: https://issues.jboss.org/browse/DROOLS-2922 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > 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, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases from the DMN canvas view, as a user I want to: > * Search a list of available data types from a decision table, as part of an input/selection process. > * Select a data type inline from a decision table. > * Have a means to rename the Decision (node.) > * Have a means to access the Manage Data Types dialog. > Notes: > Design requires a Pop-over, which includes: > * Form field labels for usability (context) and accessibility. > * Variant 1 of the PF pop-over patterns, which supports a the pop-up title. > * Drop down component with Live Search > * "Manage" link opens a dialog. > * Pop-up is initiated by a single-left mouse click within the respective decision table cell. > * Design needs to be reasonably consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2874: ------------------------------------- [~manstis] [~karreiro] Adding a pic with some callouts to sum my understanding of the agreements. The items with pink callouts are things that I assume can be added even if it can't be styled immediately, the gold ones are specific to CSS/Html styling. I will add the latter to the CSS jira: * A) Form field labels for usability (context) and accessibility. * B) Group the two actions (edit name, select data type) conceptually under a single task (Edit Decision) which is the pop-up title. * C) Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. * D) Data type selector with "Live Search" type-ahead. Note: dropdown should expand within the pop-over. * E & F) Use variant 1 of the PF pop-over patterns, which includes a title, pointer, and close icon. !pop-overcSpecs.png|thumbnail! > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > 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, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2874: -------------------------------- Attachment: pop-overcSpecs.png > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > 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, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; should be ramping-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Fix Version/s: (was: 14.0.0.CR1) > New mod_cluster nodes can become overloaded; should be ramping-up > ----------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 15.0.0.Alpha1 > > > Solved leveraging MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; should be ramping-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Fix Version/s: 15.0.0.Alpha1 > New mod_cluster nodes can become overloaded; should be ramping-up > ----------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 15.0.0.Alpha1 > > > Solved leveraging MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 August 2018