August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2874: ------------------------------------- Great, thanks [~manstis]! I'll create a CSS UX jira, for the backlog. I'm not sure when [~srambach] might be able to take it on - when you you need it by? > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2874: ---------------------------------------- [~uxdlc] Looks good to me... can UX help with the HTML markup for it? > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-2888 at 8/23/18 2:26 PM: -------------------------------------------------------------- updated click-thru (contextual menus): https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/52e0e77e/design/dtDemoAddO... as well as documentation: https://docs.google.com/document/d/1Vf3IemHMhwXUG4tZYSaAyVTSTEiC31lE2dFw-... was (Author: uxdlc): updated click-thru (contextual menus): https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/52e0e77e/design/dtDemoAddO... > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, Screen Shot 2018-08-23 at 8.47.07 AM.png, dataType4.pdf, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2888: ------------------------------------- updated click-thru (contextual menus): https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/52e0e77e/design/dtDemoAddO... > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, Screen Shot 2018-08-23 at 8.47.07 AM.png, dataType4.pdf, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic edited comment on WFWIP-119 at 8/23/18 1:58 PM: ---------------------------------------------------------------- for my own record: started a build https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... with my branch debug-replica branch: ommit 6524a2d605eb5f0c00c7fe2dac2baa1b3ee13e47 Author: Clebert Suconic <clebertsuconic(a)apache.org> Date: Thu Aug 23 13:45:31 2018 -0400 do not flush contexts was (Author: clebert.suconic): for my own record: started a build https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... with my branch debug-replica branch: ommit 6524a2d605eb5f0c00c7fe2dac2baa1b3ee13e47 Author: Clebert Suconic <clebertsuconic(a)apache.org> Date: Thu Aug 23 13:45:31 2018 -0400 do not flush contexts > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- for my own record: started a build https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... with my branch debug-replica branch: ommit 6524a2d605eb5f0c00c7fe2dac2baa1b3ee13e47 Author: Clebert Suconic <clebertsuconic(a)apache.org> Date: Thu Aug 23 13:45:31 2018 -0400 do not flush contexts > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4062) Restore PersistentResourceDefinition constructor that takes its own Parameters type

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-4062: ---------------------------------------- Summary: Restore PersistentResourceDefinition constructor that takes its own Parameters type Key: WFCORE-4062 URL: https://issues.jboss.org/browse/WFCORE-4062 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker My WFCORE-4040 PR changed the type of the Parameters param to the PersistentResourceDefinition constructor from it's own Parameters to the superclass one. That will break code that uses the old method and isn't recompiled. So, add a new overloaded constructor that takes the old type, and deprecate it. I hit this when building full today. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4062) Restore PersistentResourceDefinition constructor that takes its own Parameters type

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4062?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4062: ------------------------------------- Fix Version/s: 6.0.0.CR4 > Restore PersistentResourceDefinition constructor that takes its own Parameters type > ----------------------------------------------------------------------------------- > > Key: WFCORE-4062 > URL: https://issues.jboss.org/browse/WFCORE-4062 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 6.0.0.CR4 > > > My WFCORE-4040 PR changed the type of the Parameters param to the PersistentResourceDefinition constructor from it's own Parameters to the superclass one. That will break code that uses the old method and isn't recompiled. So, add a new overloaded constructor that takes the old type, and deprecate it. > I hit this when building full today. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-2874 at 8/23/18 1:49 PM: -------------------------------------------------------------- [~manstis] [~tirelli] I revised the pop-over to include: * Form field labels for usability (context) and [accessibility|https://www.w3.org/WAI/tutorials/forms/labels/]. * Chose to use variant 1 of the [PF pop-over patterns|https://www.patternfly.org/pattern-library/widgets/#popover]. Reasoning: Because the form contains both the decision name and the Data type selector, I believe it would be helpful to the user if we grouped these actions in a single task (Edit Decision) which is the pop-up title. [~stetson.robinson] Do you agree, and if so do you have a recommendation for the title of this form? * Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. Would need to be anchored to the top/bottom I guess to always show regardless of search results. Please add comments, will iterate as needed based on feedback. Thanks! !pop-overc.png|thumbnail! was (Author: uxdlc): [~manstis] [~tirelli] I revised the pop-over to include: * Form field labels for usability (context) and [accessibility|https://www.w3.org/WAI/tutorials/forms/labels/]. * Chose to use variant 1 of the [PF pop-over patterns|https://www.patternfly.org/pattern-library/widgets/#popover]. Reasoning: Because the form contains both the decision name and the Data type selector, I believe it would be helpful to the user if we grouped these actions in a single task (Edit Decision) or etc. [~stetson.robinson] Do you agree, and if so do you have a recommendation for the title of this form? * Added a "Manage" link outside of the dropdown element - because with the Live Search it might overload the affordance to also offer an inline action link within the list. Would need to be anchored to the top/bottom I guess to always show regardless of search results. Please add comments, will iterate as needed based on feedback. Thanks! !pop-overc.png|thumbnail! > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2916) UX design for the contextual menus

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2916?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-2916: ------------------------------------------ [~uxdlc] [~danielezonca] Hi Liz, surely there have been a misunderstanding, probably we did not explain well; this is what we said: "- click on one of Given columns -> add before given column, add after given column, remove given column - click on one of Expected columns -> add before expected column, add after expected column, remove expected column - click on a cell -> add row, remove row - click on index of the row -> duplicate row before, duplicate row after, delete row" With "click on a cell" we meant an "editable" cell of the row With "click on index of the row" we meant the leftmost cell of a row (the one with the index, not editable). This way the user has to do only one click to open the "SCENARIO" menu (in your proposal, the user first have to left-click to select a row, then have to right click to have the menu) What do you think? > UX design for the contextual menus > ---------------------------------- > > Key: DROOLS-2916 > URL: https://issues.jboss.org/browse/DROOLS-2916 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2018-08-23 at 12.34.13 PM.png > > > Provide the labels for the different contextual menus retrieved on right clicking the grid: > 1) click on a "header" cell > 2) click on the first cell of a row > 3) click on any other cell of a row -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 August 2018