[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3169?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3169:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Last Context Entry differentiation
> -------------------------------------------------
>
> Key: DROOLS-3169
> URL: https://issues.redhat.com/browse/DROOLS-3169
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot 2018-10-23 18.37.56.png, Screenshot from 2018-10-22 17-35-07.png
>
>
> The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change.
> We should improve this in one of the following ways:
> - Keep name *Default*, change font to italics and use grey background color
> - Merge the *Default* and *Value* cells of last entry and remove the name *Default*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (DROOLS-4678) Update Decision table (select type) cell hint text.
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4678?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-4678:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> Update Decision table (select type) cell hint text.
> ---------------------------------------------------
>
> Key: DROOLS-4678
> URL: https://issues.redhat.com/browse/DROOLS-4678
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-10-23 at 3.30.22 PM.png, Screen Shot 2019-10-23 at 3.38.44 PM.png, Screen Shot 2019-10-23 at 3.39.21 PM.png
>
>
> Provide clearer guidance text to the user when being asked to make a Logic type selection. Short term solutions include:
> * Revise the hint text wording to "Select logic type."
> *For consideration:*
> * Provide a tooltip on hover to instruct the user to click the cell and make a selection.
> * Consider changing the text color to blue to indicate that it's interactive. *Note although this should probably done consistently on all cells that spawn a pop-over on click...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4033?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-4033:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Save Stunners MagnetConnector.auto property
> ----------------------------------------------------------
>
> Key: DROOLS-4033
> URL: https://issues.redhat.com/browse/DROOLS-4033
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.21.0.Final
>
> Attachments: before-saved.png, re-opened.png
>
>
> 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.13.8#713008)
4 years, 9 months
[JBoss JIRA] (DROOLS-3273) [DMN Designer] Literal Expression: Font consistency
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3273?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3273:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Literal Expression: Font consistency
> ---------------------------------------------------
>
> Key: DROOLS-3273
> URL: https://issues.redhat.com/browse/DROOLS-3273
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Reported by [~tirelli]:
> {quote}
> Literal expressions currently use very different fonts and sizes when editing and when presenting. This looks really odd. Also, if the text of the literal expression goes past the border, it is presented clipped, without any visual clue that the expression was clipped.
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (DROOLS-3634) [DMN Designer] Decision Table: OutputClause improvements
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3634?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3634:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Decision Table: OutputClause improvements
> --------------------------------------------------------
>
> Key: DROOLS-3634
> URL: https://issues.redhat.com/browse/DROOLS-3634
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> The {{Name}} and {{TypeRef}} of {{OutputClauses}} should be components of the parents {{TypeRef}}. For example a {{Decision}} has a {{TypeRef}} of {{tPerson}} that is a structure with fields {{age}}/{{number}} and {{name}}/{{string}}. {{OutputClause}}'s should be defined for {{age}}/{{number}} and {{name}}/{{string}} by default.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (JGRP-2402) SOS report
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2402:
--------------------------------
This could be done in a separate protocol ({{SOS)}}? It would be configurable with a time interval and a list of protocols and their attributes to be fetched. This list could be updated by reading them from an external list.
> SOS report
> ----------
>
> Key: JGRP-2402
> URL: https://issues.redhat.com/browse/JGRP-2402
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.2.2, 5.0.0.Alpha4
>
>
> Add the ability to dump the most important attributes to a file / log (configurable), e.g.:
> * Max threads
> * Number of rejected messages
> * Size of retransmission tables (NAKACK2, UNICAST3)
> This should be done periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan.
> These files can then be sent to support via an SOS report.
> This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months