[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-3169?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-3169.
-------------------------------
Fix Version/s: 7.36.0.Final
Resolution: Won't Do
No input for ~2 years. Not reported by customer.
> [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
> Fix For: 7.36.0.Final
>
> 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)
6 years, 3 months
[JBoss JIRA] (DROOLS-3200) [DMN Designer] Properties Panel Hints
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-3200?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-3200.
-------------------------------
Resolution: Won't Fix
> [DMN Designer] Properties Panel Hints
> -------------------------------------
>
> Key: DROOLS-3200
> URL: https://issues.redhat.com/browse/DROOLS-3200
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Following DROOLS-3145 we need to identify most important fields set via properties panel and provide hints directly in the properties panel to support self-documentary product effort.
> The hints should shortly explain the fields and provide sample valid values if applicable.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2403.
----------------------------
Resolution: Done
Thread dumps are done only *once*: when the pool is full for the first time.
Once {{thread_dump}} is reset, next time around another thread dump will be logged at FATAL level.
To enable the next thread dump: {{probe.sh op=TP.resetThreadDump}}
> Dump information in panic scenarios
> -----------------------------------
>
> Key: JGRP-2403
> URL: https://issues.redhat.com/browse/JGRP-2403
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.2.2, 5.0.0.Alpha4
>
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
> The question is *when* do we do this? If the pool fluctuates between almost-full and full, we can't obviously take a thread dump every time!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months