August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-378) Random TAG is being generated on deploying from kiali/kiali

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-378?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-378. ---------------------------------- Resolution: Done returned back random tag for PR/branch builds > Random TAG is being generated on deploying from kiali/kiali > ----------------------------------------------------------- > > Key: SWSQE-378 > URL: https://issues.jboss.org/browse/SWSQE-378 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Hayk Hovsepyan > > The random tag was included because the images weren't been overridden, but when we are deploying from "kiali/kiali" the exactly tag should be matched > Example: Using Docker tag v0.6.0YWZk from Docker Repo docker.io/kiali/kiali from (http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...) > YWZk is the random component. > This need to be switched when are using kialiqe/kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2876) Data Type list icons - visual design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2876?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2876: ------------------------------------- [~karreiro] Thanks for the definitions! Could you list the font awesome icons that we're currently using? I forgot which fa-icons we decided to use. [~bdellasc] could review and let us know if they're OK. > Data Type list icons - visual design > ------------------------------------ > > Key: DROOLS-2876 > URL: https://issues.jboss.org/browse/DROOLS-2876 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: Screen Shot 2018-08-10 at 9.22.23 AM.png > > > DMN Data Types dialog uses the following PF pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/. As such it includes a list. We need list icons for two types of list items: > - Simple custom Data Types (basically means not nested date types) > - Structured custom Data Types (basically means nested data types) > Design documented in detail at: https://issues.jboss.org/browse/DROOLS-2787 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2876) Data Type list icons - visual design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2876?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2876: -------------------------------- Sprint: 2018 Week 36-38 > Data Type list icons - visual design > ------------------------------------ > > Key: DROOLS-2876 > URL: https://issues.jboss.org/browse/DROOLS-2876 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: Screen Shot 2018-08-10 at 9.22.23 AM.png > > > DMN Data Types dialog uses the following PF pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/. As such it includes a list. We need list icons for two types of list items: > - Simple custom Data Types (basically means not nested date types) > - Structured custom Data Types (basically means nested data types) > Design documented in detail at: https://issues.jboss.org/browse/DROOLS-2787 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2728) UX for custom data-types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-2728 at 8/29/18 2:25 PM: -------------------------------------------------------------- [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! Oops, nevermind - there are 2 stories (Visual Design and CSS) within the Epic that are still open. was (Author: uxdlc): [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! > UX for custom data-types > ------------------------ > > Key: DROOLS-2728 > URL: https://issues.jboss.org/browse/DROOLS-2728 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png > > > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2728) UX for custom data-types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2728: ------------------------------------- [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! > UX for custom data-types > ------------------------ > > Key: DROOLS-2728 > URL: https://issues.jboss.org/browse/DROOLS-2728 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png > > > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-410) IIOPMetaDataParser must support both legacy and new parsing routines

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-410?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-410: ---------------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/124 > IIOPMetaDataParser must support both legacy and new parsing routines > -------------------------------------------------------------------- > > Key: JBMETA-410 > URL: https://issues.jboss.org/browse/JBMETA-410 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 11.0.1.Final > > > With fix of [BZ-1192591] legacy iiop config parsing routine was discontinued. > Due to backward compatibility issues we need to support both legacy and > new parsing routines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-410) IIOPMetaDataParser must support both legacy and new parsing routines

by Richard Opalka (JIRA)

Richard Opalka created JBMETA-410: ------------------------------------- Summary: IIOPMetaDataParser must support both legacy and new parsing routines Key: JBMETA-410 URL: https://issues.jboss.org/browse/JBMETA-410 Project: JBoss Metadata Issue Type: Bug Components: ejb Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 11.0.1.Final With fix of [BZ-1192591] legacy iiop config parsing routine was discontinued. Due to backward compatibility issues we need to support both legacy and new parsing routines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 resolved DROOLS-2874. --------------------------------- Resolution: Done Reviewed by PO, OK'd to "Resolve." > 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, Screen Shot 2018-08-24 at 8.38.37 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, 8 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 commented on DROOLS-2874: ------------------------------------- Thanks [~tirelli]! > 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, Screen Shot 2018-08-24 at 8.38.37 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, 8 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 resolved DROOLS-2888. --------------------------------- Resolution: Done Reviewed by PO, OK'd to "Resolve." > 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, 8 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