[JBoss JIRA] (DROOLS-3665) [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Time" component when the type is "Time"
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3665:
------------------------------------------
Summary: [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Time" component when the type is "Time"
Key: DROOLS-3665
URL: https://issues.jboss.org/browse/DROOLS-3665
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Daniel José dos Santos
Attachments: 2.0.png, 2.1.png
When the type of the Data Type is "Time", add the "Time" component to the input, as the following mockup shows:
!2.0.png|thumbnail!
!2.1.png|thumbnail!
⚠️ Notice:
The time component is composed by:
- 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)
7 years, 2 months
[JBoss JIRA] (DROOLS-3529) [DMN Designer] Data Types - Constraints - UX improvements
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3529?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3529:
---------------------------------------
Issue Type: Enhancement (was: Task)
> [DMN Designer] Data Types - Constraints - UX improvements
> ---------------------------------------------------------
>
> Key: DROOLS-3529
> URL: https://issues.jboss.org/browse/DROOLS-3529
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> The Data Type constraints was delivered in the 7.3 in simpler version.
> This JIRA is an umbrella for all JIRAs related to UX improvements, which includes:
> - Widgets for Range constraints and every type {{Number}}, {{Day}}/Time Duration, {{Year}}/Mos Duration, {{Date}}/Time, {{Date}}, {{Time}}
> - Widgets for Enumeration constraints and every type {{Text}}, {{Number}}, {{Day}}/Time Duration, {{Year}}/Mos Duration, {{Date}}/Time, {{Date}}, {{Time}}
> - Shortcuts in the Enumeration list component (?)
> - And other small improvements that can be checked in the document attached to the comment.
> When the UX work finish, we the work on this this JIRA starts, JIRAs for each sub-task must be created.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-534) Kiali Test Mesh Operator
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-534:
------------------------------------------
Description:
Today, we do have some common situations concerning the meshes that we use to test istio and kiali
1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command.
4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support
3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific.
Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline.
was:
Today, we do have some common situations concerning the meshes that we use to test istio and kiali
1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command and also automatic injection of sidecar which is the supported way to inject sidecar on Maistra which have not been tested by the current pipeline.
3) We are going to move to Central CI Jenkins so it might be complicated to configure the slaves specific just
> Kiali Test Mesh Operator
> ------------------------
>
> Key: SWSQE-534
> URL: https://issues.jboss.org/browse/SWSQE-534
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
>
> Today, we do have some common situations concerning the meshes that we use to test istio and kiali
> 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
> 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command.
> 4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support
> 3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific.
> Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-534) Kiali Test Mesh Operator
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-534:
------------------------------------------
Summary: Kiali Test Mesh Operator (was: Mesh Operator.)
> Kiali Test Mesh Operator
> ------------------------
>
> Key: SWSQE-534
> URL: https://issues.jboss.org/browse/SWSQE-534
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
>
> Today, we do have some common situations concerning the meshes that we use to test istio and kiali
> 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
> 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command and also automatic injection of sidecar which is the supported way to inject sidecar on Maistra which have not been tested by the current pipeline.
> 3) We are going to move to Central CI Jenkins so it might be complicated to configure the slaves specific just
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-534) Mesh Operator.
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-534:
------------------------------------------
Description:
Today, we do have some common situations concerning the meshes that we use to test istio and kiali
1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command and also automatic injection of sidecar which is the supported way to inject sidecar on Maistra which have not been tested by the current pipeline.
3) We are going to move to Central CI Jenkins so it might be complicated to configure the slaves specific just
> Mesh Operator.
> --------------
>
> Key: SWSQE-534
> URL: https://issues.jboss.org/browse/SWSQE-534
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
>
> Today, we do have some common situations concerning the meshes that we use to test istio and kiali
> 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
> 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command and also automatic injection of sidecar which is the supported way to inject sidecar on Maistra which have not been tested by the current pipeline.
> 3) We are going to move to Central CI Jenkins so it might be complicated to configure the slaves specific just
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months