March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-149) The console-handler in the logging schema still contains a filter element

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-149?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reopened WFLY-149: ----------------------------------- > The console-handler in the logging schema still contains a filter element > ------------------------------------------------------------------------- > > Key: WFLY-149 > URL: https://issues.jboss.org/browse/WFLY-149 > Project: WildFly > Issue Type: Bug > Components: Localization > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-527) Remove JSR-88 support

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-527?page=com.atlassian.jira.plugin.s... ] Brian Stansberry closed WFLY-527. --------------------------------- > Remove JSR-88 support > --------------------- > > Key: WFLY-527 > URL: https://issues.jboss.org/browse/WFLY-527 > Project: WildFly > Issue Type: Sub-task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 8.0.0.Alpha1 > > > Remove JSR-88 support as it is a pruned technology. > Note: verify with [~jason.greene] before doing this one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-527) Remove JSR-88 support

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-527?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-527. ----------------------------------- Resolution: Done > Remove JSR-88 support > --------------------- > > Key: WFLY-527 > URL: https://issues.jboss.org/browse/WFLY-527 > Project: WildFly > Issue Type: Sub-task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 8.0.0.Alpha1 > > > Remove JSR-88 support as it is a pruned technology. > Note: verify with [~jason.greene] before doing this one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-527) Remove JSR-88 support

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-527?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-527: ---------------------------------- Component/s: (was: JSR88) > Remove JSR-88 support > --------------------- > > Key: WFLY-527 > URL: https://issues.jboss.org/browse/WFLY-527 > Project: WildFly > Issue Type: Sub-task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 8.0.0.Alpha1 > > > Remove JSR-88 support as it is a pruned technology. > Note: verify with [~jason.greene] before doing this one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-527) Remove JSR-88 support

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-527?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reopened WFLY-527: ----------------------------------- > Remove JSR-88 support > --------------------- > > Key: WFLY-527 > URL: https://issues.jboss.org/browse/WFLY-527 > Project: WildFly > Issue Type: Sub-task > Components: JSR88 > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 8.0.0.Alpha1 > > > Remove JSR-88 support as it is a pruned technology. > Note: verify with [~jason.greene] before doing this one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-2841?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2841: ------------------------------------- [~karreiro] Seems like it has the potential to mess things up or cause complications, but I'm probably not the best person to ask. ;) Would the bknd need to check then to make sure that the parent didn't already have a child of the same type ("name" in this case.) Or would it create instances? > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.jboss.org/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2841?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2841: --------------------------------------- Story Points: 5 (was: 1) > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.jboss.org/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2841?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2841: -------------------------------------------- [~uxdlc] When users are dragging Data Types.. should we allow them to move a DT from a parent to another? For example: {code} - tPerson(Structure) - id (Number) - tCompany(Structure) - id (Number) - name (String) {code} Are users allowed to move "{{name}}" from {{tCompant}} to {{tPerson}}? > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.jboss.org/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2841?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2841: -------------------------------------------- [~uxdlc], yes. Since I've closed the https://issues.jboss.org/browse/DROOLS-3083, DROOLS-2841 will incorporate drag and drop work. > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.jboss.org/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3784: ------------------------------------- [~dmarrazzo] WRT issues 1 & 2, perhaps contextual menus could offer a solution. I've attached two mockups, along with a supporting article. Please let me know what you think about this alternative. Thanks! !DT_List1b.png|thumbnail! !DT_List1.png|thumbnail! https://www.nngroup.com/articles/contextual-menus/ > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Liz Clayton > Priority: Minor > Labels: drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 March 2019