[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened
# check click in Navigator dock cause either selecting DRG node or opening given DRD
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode
> # Check if navigator dock can be resized
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened
# check click in Navigator dock cause either selecting DRG node or opening given DRD
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
h3. Navigation
{{//TODO}}
h3. Sorting
{{//TODO}}
h3. Undo / Redo
{{//TODO}}
h3. Synchronization
{{//TODO}}
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode
> # Check if navigator dock can be resized
> h3. Navigation
> # check *back to* link present if DRD opened
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
h3. Navigation
{{//TODO}}
h3. Sorting
{{//TODO}}
h3. Undo / Redo
{{//TODO}}
h3. Synchronization
{{//TODO}}
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
h3. Navigation
{{//TODO}}
h3. Sorting
{{//TODO}}
h3. Undo / Redo
{{//TODO}}
h3. Synchronization
{{//TODO}}
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode
> h3. Navigation
> {{//TODO}}
> h3. Sorting
> {{//TODO}}
> h3. Undo / Redo
> {{//TODO}}
> h3. Synchronization
> {{//TODO}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JGRP-2261) NPE in FD_ALL2
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2261?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2261:
---------------------------
Fix Version/s: 4.0.12
> NPE in FD_ALL2
> --------------
>
> Key: JGRP-2261
> URL: https://issues.jboss.org/browse/JGRP-2261
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: WildFly 12.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Bela Ban
> Fix For: 4.0.12
>
>
> I'm seeing a NPE in FD_ALL2 from time to time. Not consistent but the reason isn't hard to see. Stack trace:
> {code}
> 16:08:06,244 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) Exception in thread "thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)" java.lang.NullPointerException
> 16:08:06,244 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.protocols.FD_ALL2.lambda$new$0(FD_ALL2.java:83)
> 16:08:06,245 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.util.MessageBatch.replaceIf(MessageBatch.java:220)
> 16:08:06,245 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.protocols.FD_ALL2.up(FD_ALL2.java:186)
> 16:08:06,245 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.stack.Protocol.up(Protocol.java:372)
> 16:08:06,245 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.stack.Protocol.up(Protocol.java:372)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.stack.Protocol.up(Protocol.java:372)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.protocols.TP.passBatchUp(TP.java:1274)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.util.SubmitToThreadPool$BatchHandler.passBatchUp(SubmitToThreadPool.java:140)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 16:08:06,246 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 16:08:06,247 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52)
> 16:08:06,247 ERROR [stderr] (thread-10,ee,RCD_GP (flags=0), site-id=DEFAULT, rack-id=null, machine-id=null)) at java.lang.Thread.run(Thread.java:748)
> {code}
> HAS_HEADER is assuming msg is non-null, but MessageBatch makes it clear that it's valid for elements of the batch to be null, and replaceIf() doesn't perform a null check.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2424) [DMN Designer] Expression type can not be changed after cleared multiple times
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2424?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2424:
--------------------------------
Description:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2 (x)
-- 3
was:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2
-- 3
> [DMN Designer] Expression type can not be changed after cleared multiple times
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2424
> URL: https://issues.jboss.org/browse/DROOLS-2424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
>
> I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
> If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> h2. Acceptance test
> - Steps to reproduce fixed, due to code changes, check at different depth level
> -- 1 (/)
> -- 2 (x)
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2424) [DMN Designer] Expression type can not be changed after cleared multiple times
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2424?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2424:
--------------------------------
Description:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2
-- 3
was:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1
-- 2
-- 3
> [DMN Designer] Expression type can not be changed after cleared multiple times
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2424
> URL: https://issues.jboss.org/browse/DROOLS-2424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
>
> I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
> If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> h2. Acceptance test
> - Steps to reproduce fixed, due to code changes, check at different depth level
> -- 1 (/)
> -- 2
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2424) [DMN Designer] Expression type can not be changed after cleared multiple times
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2424?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2424:
--------------------------------
Description:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1
-- 2
-- 3
was:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> [DMN Designer] Expression type can not be changed after cleared multiple times
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2424
> URL: https://issues.jboss.org/browse/DROOLS-2424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
>
> I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
> If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> h2. Acceptance test
> - Steps to reproduce fixed, due to code changes, check at different depth level
> -- 1
> -- 2
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2425:
--------------------------------
Summary: [DMN Designer] Undo of relation column deletion is not proper (was: [DMN Designer] Undo of relation column is not proper)
> [DMN Designer] Undo of relation column deletion is not proper
> -------------------------------------------------------------
>
> Key: DROOLS-2425
> URL: https://issues.jboss.org/browse/DROOLS-2425
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png
>
>
> This issue was spotted during DROOLS-2392 review.
> In special cases undo of delete relation column is not proper.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month