March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3798?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3798: ------------------------------------ Story Points: 8 (was: 5) > [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3798 > URL: https://issues.jboss.org/browse/DROOLS-3798 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: daniel1.dmn, daniel2.dmn > > > When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. > --- > Assets: > - [^daniel1.dmn] > - [^daniel2.dmn] > --- > This task comprehends: > - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; > - Create the new imported nodes in the canvas; > - Persist imported nodes info properly in the DMN file (when users save it); > - Keep these imported nodes on read-only mode; > - Keep the properties panel correctly updated. > --- > Acceptance criteria: > - Open the "daniel2.dmn" > - See the imported nodes from the "daniel1.dmn" > - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) > - Check the properties panel properties > --- > [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3798?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3798: ------------------------------------ Description: When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. --- Assets: - [^daniel1.dmn] - [^daniel2.dmn] --- This task comprehends: - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; - Create the new imported nodes in the canvas; - Persist imported nodes info properly in the DMN file (when users save it); - Keep these imported nodes on read-only mode; - Keep the properties panel correctly updated. --- Acceptance criteria: - Open the "daniel2.dmn" - See the imported nodes from the "daniel1.dmn" - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) - Check the properties panel properties --- [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} was: When users open the DMN editor with an imported file, and imported nodes, they must be able to see these nodes on read-only mode. --- Assets: - [^daniel1.dmn] - [^daniel2.dmn] --- This task comprehends: - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information - Create the new imported nodes in the canvas - Persist imported nodes info properly in the DMN file (when users save it). - Keep these imported nodes on read-only mode - Keep the properties panel correctly updated --- Acceptance criteria: - Open the "daniel2.dmn" - See the imported nodes from the "daniel1.dmn" - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) - Check the properties panel properties --- [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} > [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3798 > URL: https://issues.jboss.org/browse/DROOLS-3798 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: daniel1.dmn, daniel2.dmn > > > When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. > --- > Assets: > - [^daniel1.dmn] > - [^daniel2.dmn] > --- > This task comprehends: > - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; > - Create the new imported nodes in the canvas; > - Persist imported nodes info properly in the DMN file (when users save it); > - Keep these imported nodes on read-only mode; > - Keep the properties panel correctly updated. > --- > Acceptance criteria: > - Open the "daniel2.dmn" > - See the imported nodes from the "daniel1.dmn" > - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) > - Check the properties panel properties > --- > [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-3798: --------------------------------------- Summary: [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened Key: DROOLS-3798 URL: https://issues.jboss.org/browse/DROOLS-3798 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos Attachments: daniel1.dmn, daniel2.dmn When users open the DMN editor with an imported file, and imported nodes, they must be able to see these nodes on read-only mode. --- Assets: - [^daniel1.dmn] - [^daniel2.dmn] --- This task comprehends: - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information - Create the new imported nodes in the canvas - Persist imported nodes info properly in the DMN file (when users save it). - Keep these imported nodes on read-only mode - Keep the properties panel correctly updated --- Acceptance criteria: - Open the "daniel2.dmn" - See the imported nodes from the "daniel1.dmn" - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) - Check the properties panel properties --- [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ] Matthew Mahoney commented on SWSQE-605: --------------------------------------- Note: Team reviewed the Pros/Cons doc: Decision was to stay on our current team managed Jenkins instance, for the time being. Will evaluate moving to Openshift Jenkins > Establish Central CI Jenkins Master For Kiali > --------------------------------------------- > > Key: SWSQE-605 > URL: https://issues.jboss.org/browse/SWSQE-605 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Our team at one time was allocated a Central CI Jenkins Master. > Therefore, one of the following, > Either: > a) Confirm that our team's Central CI Jenkins Master is still available and usable > Or > b) Establish a new Central CI Jenkins Master > We also need to confirm that Jenkins master in Central Ci will fit our needs like: > * is it possible to run smee.io client there to consume github events > * is it possible to install plugins we are using > * check SLA > * check backups, upgrades > * do we want to share it with istio qe team? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ] Matthew Mahoney resolved SWSQE-605. ----------------------------------- Resolution: Done > Establish Central CI Jenkins Master For Kiali > --------------------------------------------- > > Key: SWSQE-605 > URL: https://issues.jboss.org/browse/SWSQE-605 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Our team at one time was allocated a Central CI Jenkins Master. > Therefore, one of the following, > Either: > a) Confirm that our team's Central CI Jenkins Master is still available and usable > Or > b) Establish a new Central CI Jenkins Master > We also need to confirm that Jenkins master in Central Ci will fit our needs like: > * is it possible to run smee.io client there to consume github events > * is it possible to install plugins we are using > * check SLA > * check backups, upgrades > * do we want to share it with istio qe team? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3755) [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3755?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3755: ------------------------------------ Sprint: (was: 2019 Week 11-13) > [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time" > -------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3755 > URL: https://issues.jboss.org/browse/DROOLS-3755 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: datetime-dropdown.png, datetime-enum.png, datetime-range.png, datetime-time.png > > > When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows: > Enum/Range: > !datetime-enum.png|thumbnail! > !datetime-range.png|thumbnail! > Components: > !datetime-dropdown.png|thumbnail! > !datetime-time.png|thumbnail! > ⚠️ Notice: > This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665): > - An input with the timepicker; > - A toggle button (to toggle between offset and timezone) > - An input which is filled accordingly to the toggle button -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-625) Get access for kiali qe to https://gitlab.cee.redhat.com/istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-625?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-625: -------------------------------- Labels: infrastructure (was: infr) > Get access for kiali qe to https://gitlab.cee.redhat.com/istio > -------------------------------------------------------------- > > Key: SWSQE-625 > URL: https://issues.jboss.org/browse/SWSQE-625 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We agreed that we want to share one organization among istio and kiali in cee gitlab. > Note that there is already https://gitlab.cee.redhat.com/kiali-qe/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-588) Polarion Testcase Review/Edit make Up-to-date

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-588?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-588. ------------------------------------------- Resolution: Done > Polarion Testcase Review/Edit make Up-to-date > --------------------------------------------- > > Key: SWSQE-588 > URL: https://issues.jboss.org/browse/SWSQE-588 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-625) Get access for kiali qe to https://gitlab.cee.redhat.com/istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-625?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-625: -------------------------------- Labels: infr (was: infrastructure) > Get access for kiali qe to https://gitlab.cee.redhat.com/istio > -------------------------------------------------------------- > > Key: SWSQE-625 > URL: https://issues.jboss.org/browse/SWSQE-625 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infr > > We agreed that we want to share one organization among istio and kiali in cee gitlab. > Note that there is already https://gitlab.cee.redhat.com/kiali-qe/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-560) OCP 4.0 on Openstack

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-560?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-560: -------------------------------- Labels: infrastructure (was: ) > OCP 4.0 on Openstack > -------------------- > > Key: SWSQE-560 > URL: https://issues.jboss.org/browse/SWSQE-560 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > New Openshift Installer supports OpenStack (https://github.com/openshift/installer/blob/master/docs/user/openstack/RE...) > It can be a substitute for OSOOS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019