May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4033?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4033: ----------------------------------- Attachment: (was: auto-magnets.gif) > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.jboss.org/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner, drools-tools > Fix For: 7.21.0.Final > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4033?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4033: ----------------------------------- Attachment: (was: fixed-magnets.gif) > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.jboss.org/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner, drools-tools > Fix For: 7.21.0.Final > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4033?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4033: ----------------------------------- Attachment: (was: process-designer-connectors-magnets-issues.png) > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.jboss.org/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner, drools-tools > Fix For: 7.21.0.Final > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4033?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4033: ----------------------------------- Attachment: (was: weird_arrow.gif) > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.jboss.org/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner, drools-tools > Fix For: 7.21.0.Final > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4033?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4033: ----------------------------------- Description: Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. was: 1. Add a `Decision Node` 2. Add a `Input Data Node` bellow `Decision Node` 3. Connect `Input Data Node` to `Decision Node` 4. Save 5. Close 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. I noticed this in DMN Showcase and in drools-wb. And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.jboss.org/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner, drools-tools > Fix For: 7.21.0.Final > > Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4034) Add an Instance to a Scenario Column leads to an exception

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4034?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4034: ------------------------------- Sprint: 2019 Week 20-22 > Add an Instance to a Scenario Column leads to an exception > ---------------------------------------------------------- > > Key: DROOLS-4034 > URL: https://issues.jboss.org/browse/DROOLS-4034 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > Open a new TestScenario editor. > Try to assign an instance to a column. Instance only, without a property (eg. Author). > An exception is thown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4034) Add an Instance to a Scenario Column leads to an exception

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4034: ---------------------------------- Summary: Add an Instance to a Scenario Column leads to an exception Key: DROOLS-4034 URL: https://issues.jboss.org/browse/DROOLS-4034 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Yeser Amer Assignee: Yeser Amer Open a new TestScenario editor. Try to assign an instance to a column. Instance only, without a property (eg. Author). An exception is thown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4034) Add an Instance to a Scenario Column leads to an exception

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4034?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4034: ------------------------------- Story Points: 1 > Add an Instance to a Scenario Column leads to an exception > ---------------------------------------------------------- > > Key: DROOLS-4034 > URL: https://issues.jboss.org/browse/DROOLS-4034 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > Open a new TestScenario editor. > Try to assign an instance to a column. Instance only, without a property (eg. Author). > An exception is thown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4033: -------------------------------------- Summary: [DMN Designer] Save Stunners MagnetConnector.auto property Key: DROOLS-4033 URL: https://issues.jboss.org/browse/DROOLS-4033 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Daniel José dos Santos Assignee: Michael Anstis Fix For: 7.21.0.Final Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif 1. Add a `Decision Node` 2. Add a `Input Data Node` bellow `Decision Node` 3. Connect `Input Data Node` to `Decision Node` 4. Save 5. Close 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. I noticed this in DMN Showcase and in drools-wb. And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-668) Checklist for custom fields in order to support existing and future workflows for Istio

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-668?page=com.atlassian.jira.plugin.... ] Prachi Yadav commented on SWSQE-668: ------------------------------------ [~yuaxu] We have this available in JIRA and we were looking for that. For now I have provided the information to the team so this issue is resolved now > Checklist for custom fields in order to support existing and future workflows for Istio > --------------------------------------------------------------------------------------- > > Key: SWSQE-668 > URL: https://issues.jboss.org/browse/SWSQE-668 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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