[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3023:
---------------------------------------
Attachment: prototype.png
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: prototype.png
>
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
> h2. Manual acceptance test
> Check warning list all occurrences:
> - Remove item definition used as part of other item definitions
> -- Top level, all occurences removed
> -- Nested level, top level definition remains
> - Remove item definitions used as output data-type for decision node
> - Remove item definition used as data-type for expression element (column, parameter, ...)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2762:
---------------------------------------
Description:
The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
- This component must be disabled (or hidden) when an existing/primitive data type is selected.
h3. Acceptance test
- User not able to add and save lines that are filled just partially (this requirement will be addressed by the https://issues.jboss.org/browse/DROOLS-3022)
- Check added rows after reopening
- The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
was:
The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
- This component must be disabled (or hidden) when an existing/primitive data type is selected.
h3. Acceptance test
- User not able to add and save lines that are filled just partially
- Check added rows after reopening
- The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
> [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2762
> URL: https://issues.jboss.org/browse/DROOLS-2762
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2762.png
>
>
> The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
> - This component must be disabled (or hidden) when an existing/primitive data type is selected.
> h3. Acceptance test
> - User not able to add and save lines that are filled just partially (this requirement will be addressed by the https://issues.jboss.org/browse/DROOLS-3022)
> - Check added rows after reopening
> - The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3022:
---------------------------------------
Summary: [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name (was: [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name)
> [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
> h2. Manaul Acceptance Test
> - Try to put same name by Typing
> - Try to put same name by Copy and paste
> - Do not allow empty name
> - Allow spaces in name
> - Allow multibyte chars in name
> - Allow special characters in name (?)
> - Allow lower upper case in name
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3035) Implement meaningful access to "significant" header metadata
by Gabriele Cardosi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3035?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3035:
-------------------------------------
Summary: Implement meaningful access to "significant" header metadata (was: Implement meaningful access to "significative" header metadata)
> Implement meaningful access to "significant" header metadata
> ------------------------------------------------------------
>
> Key: DROOLS-3035
> URL: https://issues.jboss.org/browse/DROOLS-3035
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> Subclass BaseGridColumn to add a "getSignificativeHeader" (find a better name) to retrieve the header with the "group" information.
> This is to avoid the meaningless and error-prone getHeaderMetadata().get(index) (it broke for column with a number of headermetadata different then expected)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3035) Implement meaningful access to "significant" header metadata
by Gabriele Cardosi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3035?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3035:
-------------------------------------
Description:
Subclass BaseGridColumn to add a "getSignificantHeader" (find a better name) to retrieve the header with the "group" information.
This is to avoid the meaningless and error-prone getHeaderMetadata().get(index) (it broke for column with a number of headermetadata different then expected)
was:
Subclass BaseGridColumn to add a "getSignificativeHeader" (find a better name) to retrieve the header with the "group" information.
This is to avoid the meaningless and error-prone getHeaderMetadata().get(index) (it broke for column with a number of headermetadata different then expected)
> Implement meaningful access to "significant" header metadata
> ------------------------------------------------------------
>
> Key: DROOLS-3035
> URL: https://issues.jboss.org/browse/DROOLS-3035
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> Subclass BaseGridColumn to add a "getSignificantHeader" (find a better name) to retrieve the header with the "group" information.
> This is to avoid the meaningless and error-prone getHeaderMetadata().get(index) (it broke for column with a number of headermetadata different then expected)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3035) Implement meaningful access to "significative" header metadata
by Gabriele Cardosi (JIRA)
Gabriele Cardosi created DROOLS-3035:
----------------------------------------
Summary: Implement meaningful access to "significative" header metadata
Key: DROOLS-3035
URL: https://issues.jboss.org/browse/DROOLS-3035
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Priority: Minor
Subclass BaseGridColumn to add a "getSignificativeHeader" (find a better name) to retrieve the header with the "group" information.
This is to avoid the meaningless and error-prone getHeaderMetadata().get(index) (it broke for column with a number of headermetadata different then expected)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-433) New user and namespace should be created in B24 for jaeger pipeline tests
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-433?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo resolved SWSQE-433.
-------------------------------------------
Resolution: Done
[~jkandasa]
Done.
Created user 'jaegeruser' and namespace jaegerpipeline with deployer permissions on this specific namespace.
> New user and namespace should be created in B24 for jaeger pipeline tests
> -------------------------------------------------------------------------
>
> Key: SWSQE-433
> URL: https://issues.jboss.org/browse/SWSQE-433
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Jeeva Kandasamy
> Assignee: Guilherme Baufaker Rêgo
>
> Jaeger developer needs a jenkins+jaegertracing environment in Openshift environment for some time. (to setup jenkins pipline to automate productisation)
> For now(next few months), we can create a temporary namespace and user in B24 (where we running all our Jaeger tests).
> This setup will be used by Gary for some time (until we complete the first level of a pipeline for jaeger productisation).
> Username: jaegeruser
> Namespace: jaeger-pipeline
> Original ticket: https://issues.jboss.org/browse/TRACING-241
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months