January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2697) [DMN Designer] Improve readability of node labels

by Matthew Stevens (Jira)

[ https://issues.jboss.org/browse/DROOLS-2697?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-2697: ----------------------------------------- I agree, this is great. Thank you [~dadossan]! > [DMN Designer] Improve readability of node labels > ------------------------------------------------- > > Key: DROOLS-2697 > URL: https://issues.jboss.org/browse/DROOLS-2697 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Attachments: BPMN-label.png, Resize_live.gif, node_label.gif, screenshot-1.png, screenshot-2.png > > > Node names are bold text without background rectangle and hence _merge_ into the node SVG. It'd be nicer to change font to regular and provide a (white) background rectangle to improve readability. See https://github.com/kiegroup/kie-wb-common/pull/1929#pullrequestreview-133... > h2. Acceptance criteria > - Download as DMN, import into external tool > - Download as picture -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11595) Eliminate unnecessary remote command invocation when EJB has no @StatefulTimeout

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11595: ----------------------------------- Summary: Eliminate unnecessary remote command invocation when EJB has no @StatefulTimeout Key: WFLY-11595 URL: https://issues.jboss.org/browse/WFLY-11595 Project: WildFly Issue Type: Bug Components: Clustering, EJB Affects Versions: 15.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3454: -------------------------------- Sprint: 2019 Week 02-04 > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3454: -------------------------------- Story Points: 2 (was: 3) > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-134) Should be some kind of indication of bad message format String

by Steve Ebersole (Jira)

Steve Ebersole created JBLOGGING-134: ---------------------------------------- Summary: Should be some kind of indication of bad message format String Key: JBLOGGING-134 URL: https://issues.jboss.org/browse/JBLOGGING-134 Project: JBoss Logging Issue Type: Enhancement Affects Versions: 3.3.2.Final Reporter: Steve Ebersole Assignee: James Perkins At the moment, when a log message contains a bad formatting String JBoss Logging simply "skips" the message. There is no output and there is not warning. From the outside, the log statement is just effectively ignored. Perhaps caused by JBLOGGING-75. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3446: ------------------------------------- Note: Kebab menu for "enumeration" should include: * edit * move up * move down > Data type constraints: Basic interaction/workflow > ------------------------------------------------- > > Key: DROOLS-3446 > URL: https://issues.jboss.org/browse/DROOLS-3446 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * From the Data Types tab: > As a user I want the ability to define constraints for data type definitions in use within the DMN file. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3455: ------------------------------------- Thanks [~karreiro]. [~tirelli] may I mark this as Resolved? > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3458) Data type constraints: Text

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3458?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3458: ------------------------------------- Thanks [~karreiro]. [~tirelli] may I mark this as Resolved? > Data type constraints: Text > --------------------------- > > Key: DROOLS-3458 > URL: https://issues.jboss.org/browse/DROOLS-3458 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Text (Expression and Enumeration.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3457) Data type constraints: Boolean

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3457?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3457: ------------------------------------- Thanks [~karreiro], I missed that. I'll close this jira then. > Data type constraints: Boolean > ------------------------------ > > Key: DROOLS-3457 > URL: https://issues.jboss.org/browse/DROOLS-3457 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: boolean-enumeration.png, boolean-expression.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Number (Expression and Enumeration.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3457) Data type constraints: Boolean

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3457?page=com.atlassian.jira.plugi... ] Liz Clayton closed DROOLS-3457. ------------------------------- Resolution: Done not required, per [~tirelli] > Data type constraints: Boolean > ------------------------------ > > Key: DROOLS-3457 > URL: https://issues.jboss.org/browse/DROOLS-3457 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: boolean-enumeration.png, boolean-expression.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Number (Expression and Enumeration.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 January 2019