April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1954) [DMN Editor] Keyboard shortcuts

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1954?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1954: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > [DMN Editor] Keyboard shortcuts > ------------------------------- > > Key: DROOLS-1954 > URL: https://issues.jboss.org/browse/DROOLS-1954 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The DMN editor could support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1942: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1964) [DMN Editor] Input Data typeRef

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1964?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1964: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > [DMN Editor] Input Data typeRef > ------------------------------- > > Key: DROOLS-1964 > URL: https://issues.jboss.org/browse/DROOLS-1964 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > The Input Data nodes specifies the datatype via _typeRef_ attribute. Allowed are simple datatypes, enumerations of allowed values and complex data types like Person. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX, UXTeam > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2255) [DMN designer] Node labels move between savings

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2255?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2255: ----------------------------------- Sprint: 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14) > [DMN designer] Node labels move between savings > ----------------------------------------------- > > Key: DROOLS-2255 > URL: https://issues.jboss.org/browse/DROOLS-2255 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Wagner Scholl Lemos > Priority: Critical > Labels: Stunner > Attachments: after-save.png, before-save.png > > > The attachments shows DMN diagram before and after saving, it can be seen that node labels moved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.8.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2462) kie-docs 6.5.x doesn't build offline

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2462?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer reassigned DROOLS-2462: ---------------------------------------------- Assignee: Marek Novotny > kie-docs 6.5.x doesn't build offline > ------------------------------------ > > Key: DROOLS-2462 > URL: https://issues.jboss.org/browse/DROOLS-2462 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 6.5.0.Final > Reporter: Michael Biarnes Kiefer > Assignee: Marek Novotny > > when the repository kie-docs 6.5.x is build offline > _man clean install -Dfull -o_ (and without internet connection) this error is thrown: [error|https://gist.github.com/mbiarnes/bb3a46bebf788225f663f249fc9dc361] > The general suspicion is that <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.76.1/fo/docbook.xsl"/> can't be downloaded and this causes the error. > We have on Jenkins each "some days" period that kie-docs fails, but when building again it builds successful. So when it fails it has no connection problems and this file can't be downloaded. > A build without internet connection is not possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-129) Reinstall Openshift on B12

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-129: ------------------------------------ Summary: Reinstall Openshift on B12 Key: SWSQE-129 URL: https://issues.jboss.org/browse/SWSQE-129 Project: Kiali QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Priority: Blocker -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-128) Reinstall Openshift on B11

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-128: ------------------------------------ Summary: Reinstall Openshift on B11 Key: SWSQE-128 URL: https://issues.jboss.org/browse/SWSQE-128 Project: Kiali QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Priority: Blocker -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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