[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-3053 at 10/4/18 2:28 PM:
-------------------------------------------------------------------
[~uxdlc], I like it! Verbose can be good if it clarifies. What do you think about this instead:
---
This column contains Scenario input values that might not correspond with the new values after this change. Select how you want to continue.
- Preserve existing Scenario values in this column.
- Clear all Scenario values in this column.
---
was (Author: stetson.robinson):
[~uxdlc], I like it! Verbose can be good if it clarifies. What do you think about this instead:
This column contains Scenario input values that might not correspond with the new values after this change. Select how you want to continue.
- Preserve existing Scenario values in this column.
- Clear all Scenario values in this column.
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-3053 at 10/4/18 2:28 PM:
-------------------------------------------------------------------
[~uxdlc], I like it! Verbose can be good if it clarifies. What do you think about this instead:
---
This column contains Scenario input values that might not correspond with the new values after this change. Select how you want to continue.
- Preserve existing Scenario values in this column.
- Clear all Scenario values in this column.
---
was (Author: stetson.robinson):
[~uxdlc], I like it! Verbose can be good if it clarifies. What do you think about this instead:
---
This column contains Scenario input values that might not correspond with the new values after this change. Select how you want to continue.
- Preserve existing Scenario values in this column.
- Clear all Scenario values in this column.
---
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2788:
-------------------------------------
[~danielezonca] I'm confused about your comment regarding "expression builder component" - doesn't the tree as designed offer the ability to cover both? Click on the parent node to select the top-level data object, or click on a field within it?
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2788:
-------------------------------------
[~danielezonca] I am trying to address the use case in the description of this jira: "As a user I want to define multiple data/domain object instances per scenario..., so that I can create a test scenario."
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
If Expect column, then Expect...
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
[~stetson.robinson] [~srambach] @gadey(a)redhat.com
It's a tad verbose, but I for the 2nd scenario (above) I was thinking about something like this, wdyt?
!warning.png|thumbnail!
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3053:
--------------------------------
Attachment: warning.png
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (LOGMGR-201) SysLogHandler doesn't log null or empty message
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-201?page=com.atlassian.jira.plugin... ]
James Perkins reassigned LOGMGR-201:
------------------------------------
Assignee: James Perkins
Resolution: Rejected
> SysLogHandler doesn't log null or empty message
> -----------------------------------------------
>
> Key: LOGMGR-201
> URL: https://issues.jboss.org/browse/LOGMGR-201
> Project: JBoss Log Manager
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1.4.Final
> Reporter: Vladyslav Baidak
> Assignee: James Perkins
> Priority: Major
> Fix For: 2.1.5.Final
>
>
> For cases when message is *null* or *empty*, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish_ method)
> I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler:
> {code:java}
> 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException
> at java.util.Optional.orElseThrow(Optional.java:290)
> at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28)
> at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
> As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (LOGMGR-201) SysLogHandler doesn't log null or empty message
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-201?page=com.atlassian.jira.plugin... ]
James Perkins reopened LOGMGR-201:
----------------------------------
> SysLogHandler doesn't log null or empty message
> -----------------------------------------------
>
> Key: LOGMGR-201
> URL: https://issues.jboss.org/browse/LOGMGR-201
> Project: JBoss Log Manager
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1.4.Final
> Reporter: Vladyslav Baidak
> Assignee: James Perkins
> Priority: Major
> Fix For: 2.1.5.Final
>
>
> For cases when message is *null* or *empty*, *SysLogHandler* doesn't publish event (there is a correspondent logic in _doPublish_ method)
> I expect even *null* or *empty* messages to be sent. Consider the following message logged to CONSOLE handler:
> {code:java}
> 21:21:27,562 ERROR [ch.mobi.jes.jaxrs.exception.converter.internal.mapper.AbstractThrowableMapper] (default task-1) null: java.lang.IllegalArgumentException
> at java.util.Optional.orElseThrow(Optional.java:290)
> at ch.mobi.apsbau.pdfservice.entity.guarantee.GuaranteeType.resolve(GuaranteeType.java:36)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toGuaranteeType(GuaranteeMapper.java:43)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapperImpl.toDraftDtoInternal(GuaranteeMapperImpl.java:49)
> at ch.mobi.apsbau.pdfservice.mapper.guarantee.GuaranteeMapper.toDraft(GuaranteeMapper.java:28)
> at ch.mobi.apsbau.pdfservice.boundary.guarantee.GuaranteeResourceImpl.generateDraft(GuaranteeResourceImpl.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
> As you can see from example above, the message is null and as a result the entire stacktrace is skipped and not published
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3053:
------------------------------------------
[~uxdlc][~stetson.robinson]
Hi!
We have to show different popup for the following conditions:
- no data in the column => safe to change and no confirmation needed (no popup shown)
- existing data are of the same type of the new one (i.e. String to String) => confirmation message with keep existing data, remove existing data or cancel the action
- existing data are of different type => confirmation message that existing data will be removed or cancel the action
Currently implemented popup are
!Screenshot from 2018-10-04 17-44-51.png|thumbnail!
!Screenshot from 2018-10-04 17-45-21.png|thumbnail!
Messages, labels, and button colors may be changed.
Please let us know your proposal. Thanks.
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months