February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5058) [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5058?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5058: -------------------------------- Description: h2. Manual acceptance test h3. Business central Edit in parallel passed but seems the performance is decreased [^switch-dmn.webm] # Two dmn files, two decisions (/) # Two dmn files, decision and bkm (/) # One dmn file, decision table and context (/) h3. VS Code Edit in parallel # Two dmn files, two decisions (?) # Two dmn files, decision and bkm (?) # One dmn file, decision table and context (?) was: h2. Manual acceptance test h3. Business central Edit in parallel # Two dmn files, two decisions (?) # Two dmn files, decision and bkm (?) # One dmn file, decision table and context (?) h3. VS Code Edit in parallel # Two dmn files, two decisions (?) # Two dmn files, decision and bkm (?) # One dmn file, decision table and context (?) > [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5058 > URL: https://issues.redhat.com/browse/DROOLS-5058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: switch-dmn.webm > > > h2. Manual acceptance test > h3. Business central > Edit in parallel passed but seems the performance is decreased [^switch-dmn.webm] > # Two dmn files, two decisions (/) > # Two dmn files, decision and bkm (/) > # One dmn file, decision table and context (/) > h3. VS Code > Edit in parallel > # Two dmn files, two decisions (?) > # Two dmn files, decision and bkm (?) > # One dmn file, decision table and context (?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5086) undo button

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5086: --------------------------------------------- Summary: undo button Key: DROOLS-5086 URL: https://issues.redhat.com/browse/DROOLS-5086 Project: Drools Issue Type: Feature Request Components: tools Reporter: Werner Van Herrewegen Assignee: Mario Fusco As a business user using the business central webapp I don't know what git is and want to have my 'undo' button that rolls back the last commit on 'my branch' when I make a mistake. tech: make sure a diff is shown and explicit validation is requested with an explicit 'confirm' button -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5085) list of triggered rules when executing test scenario

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5085: --------------------------------------------- Summary: list of triggered rules when executing test scenario Key: DROOLS-5085 URL: https://issues.redhat.com/browse/DROOLS-5085 Project: Drools Issue Type: Feature Request Components: Scenario Simulation and Testing Reporter: Werner Van Herrewegen Assignee: Daniele Zonca As a business user running a test scenario, I would like to know what rules triggered, so I know where to look when the test fails. technical implementation suggestion: the log window beneath the test is a good place. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5058) [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5058?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5058: -------------------------------- Description: h2. Manual acceptance test h3. Business central Edit in parallel # Two dmn files, two decisions (?) # Two dmn files, decision and bkm (?) # One dmn file, decision table and context (?) h3. VS Code Edit in parallel # Two dmn files, two decisions (?) # Two dmn files, decision and bkm (?) # One dmn file, decision table and context (?) > [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5058 > URL: https://issues.redhat.com/browse/DROOLS-5058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > h2. Manual acceptance test > h3. Business central > Edit in parallel > # Two dmn files, two decisions (?) > # Two dmn files, decision and bkm (?) > # One dmn file, decision table and context (?) > h3. VS Code > Edit in parallel > # Two dmn files, two decisions (?) > # Two dmn files, decision and bkm (?) > # One dmn file, decision table and context (?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5084) grouping rules

by Werner Van Herrewegen (Jira)

Werner Van Herrewegen created DROOLS-5084: --------------------------------------------- Summary: grouping rules Key: DROOLS-5084 URL: https://issues.redhat.com/browse/DROOLS-5084 Project: Drools Issue Type: Feature Request Components: tools Reporter: Werner Van Herrewegen Assignee: Mario Fusco As a business user I would like to have an easy way to +*visibly *+group certain rules together in the business central. As a business user I want to have an intuitive way to afterwards find rules related to one of those groups. constraints: I don't want to use package (physical folder structure) I don't want to use the current tags implementation as I don't use the left side 'developer' project/repository treeview multiple rules can have the same group some rules might fit under multiple groups and should thus be found under multiple 'groups' workaround: Currently I use my own naming convention to allow business people to search for rules having to do with a certain topic. But it is tedious to maintain as rule names are free text and I have no way to force them to use the convention. And also the user needs to currently guess the 'topic'-names in the rule search window instead of having a list of 'topics' suggested solution: I like the tags idea. this allows to have the many to many relationship of rules and 'rule groups' But the way it is implemented in the UI is nog user friendly enough to get business people to use it. I would also force them to put at least 1 tag. And really important, tags must be forced to ALL_CAPITALS and no special signs but must ALLOW spaces (no underscores or hyphens for business users!). When creating a rule (the popup dialog where you name the rule and select the package), that is the time to add tags to it. (and not hidden in the overview>metadata tab) And afterwards they can be amended in this overview>metadata tab (though I would recommend to name it for business users 'rule info' tab, and make it easier to find) :-) This will ensure that business people categorize their rules to keep track of them when the list gets longer. (and not get IT to find them for them) For the second part ... Now that business people have tagged their rules with 'business topics', they need to have an easy way to find all rules related to this 'business topic' (tag) The rule filter window is an excellent place for this. I would like an additional filter text box that allows a collection of tags that will be used to filter the rules list. This text box is NOT 'free text' and should be fillable only with existing tags (think of the '+search +for labels' feature in jira) ->only allow valid tags (no free text) ->allow multiple tags (logic = OR/AND(perhaps also a NOT?) : use these words between selected tags iso just using a comma) ->drop down list sorted alphabetically with remaining valid tags In the result set, it would be also nice to to have an indication of the labels that apply to the specific rules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) WF20: Upgrade HAL to 3.2.7.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13032 (was: https://github.com/wildfly/wildfly/pull/12994) > WF20: Upgrade HAL to 3.2.7.Final > -------------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 20.0.0.Beta1 > > > This component upgrade contais bug fixes only. > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.7.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13143) WF19: Upgrade HAL to 3.2.7.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13143?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13143: ------------------------------- Fix Version/s: 19.0.0.Beta3 (was: 20.0.0.Beta1) > WF19: Upgrade HAL to 3.2.7.Final > -------------------------------- > > Key: WFLY-13143 > URL: https://issues.redhat.com/browse/WFLY-13143 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > This component upgrade contais bug fixes only. > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.7.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13143) WF19: Upgrade HAL to 3.2.7.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13143?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13143: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12994) > WF19: Upgrade HAL to 3.2.7.Final > -------------------------------- > > Key: WFLY-13143 > URL: https://issues.redhat.com/browse/WFLY-13143 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > This component upgrade contais bug fixes only. > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.7.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) WF20: Upgrade HAL to 3.2.7.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Summary: WF20: Upgrade HAL to 3.2.7.Final (was: Upgrade HAL to 3.2.6.Final) > WF20: Upgrade HAL to 3.2.7.Final > -------------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 20.0.0.Beta1 > > > This component upgrade contais bug fixes only. > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.7.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13143) WF19: Upgrade HAL to 3.2.7.Final

by Harald Pehl (Jira)

Harald Pehl created WFLY-13143: ---------------------------------- Summary: WF19: Upgrade HAL to 3.2.7.Final Key: WFLY-13143 URL: https://issues.redhat.com/browse/WFLY-13143 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 20.0.0.Beta1 This component upgrade contais bug fixes only. Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.7.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020