July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4255: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > Add KIE server support for deploying custom Prometheus metrics > -------------------------------------------------------------- > > Key: DROOLS-4255 > URL: https://issues.jboss.org/browse/DROOLS-4255 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.24.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Labels: CustomerFocus > Fix For: 7.25.0.Final > > > The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4245: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Documentation - Enhance presentation > --------------------------------------------------- > > Key: DROOLS-4245 > URL: https://issues.jboss.org/browse/DROOLS-4245 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: doc.pdf, new_doc.pdf > > > Enhance styles and presentation of the Documentation output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4208) [DMN Designer] Documentation - Widget for links persisting links

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4208?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4208: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Documentation - Widget for links persisting links > ---------------------------------------------------------------- > > Key: DROOLS-4208 > URL: https://issues.jboss.org/browse/DROOLS-4208 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-4208.png > > > Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. > The widget must be just like this one: > https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 > (A list which is populated by the popover). > Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). > !DROOLS-4208.png|thumbnail! > * This is just a suggestion, the entity name can be improved. > h3. Acceptance test > On both Firefox and Chrome > - Multiple links - scroll to view all (/) > - Add multiple, delete some (/) > - Open the link (/) > - Switch between nodes (/) > - Link name - long (/) > - Link name - multibyte characters (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4209) [DMN Designer] Documentation - Persist links into extension elements

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4209?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4209: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Documentation - Persist links into extension elements > -------------------------------------------------------------------- > > Key: DROOLS-4209 > URL: https://issues.jboss.org/browse/DROOLS-4209 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > A {{DMNExternalLink}} must be persisted into the DMN file by using the {{extensionElements}} section. > This JIRAs refers to take the output from the [Widget|https://issues.jboss.org/browse/DROOLS-4208] and persist it into the model by using the {{extensionElements}} section. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4210) [DMN Designer] Documentation - Show DMNExternalLinks into the Documentation

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4210?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4210: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Documentation - Show DMNExternalLinks into the Documentation > --------------------------------------------------------------------------- > > Key: DROOLS-4210 > URL: https://issues.jboss.org/browse/DROOLS-4210 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Show all {{DMNExternalLink}}s into the Documentation tab. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4211) [DMN Designer] Search feature - Implement search mechanism PoC on GDT

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4211?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4211: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Search feature - Implement search mechanism PoC on GDT > --------------------------------------------------------------------- > > Key: DROOLS-4211 > URL: https://issues.jboss.org/browse/DROOLS-4211 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This JIRA refers to the implementation of the *search mechanism prof of concept* for Guided Decision Tables. > In this context, *prof of concept* means that: > - the search feature won't be visible in the screen > - the basic search mechanism will be working (results for a given text are being returned) > - the assignee needs to provide a way for enable this feature for PR reviewers -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4212) [DMN Designer] Search feature - Implement search mechanism PoC on DMN graph

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4212?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4212: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > [DMN Designer] Search feature - Implement search mechanism PoC on DMN graph > --------------------------------------------------------------------------- > > Key: DROOLS-4212 > URL: https://issues.jboss.org/browse/DROOLS-4212 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This JIRA refers to the implementation of the *search mechanism prof of concept* for DMN graph. > In this context, *prof of concept* means that: > - the search feature won't be visible in the screen > - the basic search mechanism will be working (results for a given text are being returned) > - the assignee needs to provide a way for enable this feature for PR reviewers -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4205: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 26-28) > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4163) Prototype of common client-side marshaller

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4163?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4163: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 23-25, 2019 Week 26-28) > Prototype of common client-side marshaller > ------------------------------------------ > > Key: DROOLS-4163 > URL: https://issues.jboss.org/browse/DROOLS-4163 > Project: Drools > Issue Type: Enhancement > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Create a common and easily-reusable mechanism to implement client-side marshalling -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3923: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31 (was: 2019 Week 23-25, 2019 Week 26-28) > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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