[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4503:
--------------------------------
Tester: Jozef Marko
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.26.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> !ErrorPopup.png|thumbnail!
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
> The worst consequence is that when user click "Apply", that literal is put inside the cell,
> !InsertedValue.png|thumbnail!
> and when sent to server it raise error (because server is expecting a number, not a string)
> !FollowError.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4518:
-----------------------------------------
Summary: Implement UX styles for Test Coverage Report
Key: DROOLS-4518
URL: https://issues.jboss.org/browse/DROOLS-4518
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Elizabeth Clayton
Assignee: Daniele Zonca
The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Attachment: Screenshot from 2019-09-10 15-27-22.png
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png, Screenshot from 2019-09-10 15-27-22.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> [2]
> -
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Description:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
[2]
- !Screenshot from 2019-09-10 15-27-22.png|thumbnail!
was:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
[2]
-
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png, Screenshot from 2019-09-10 15-27-22.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> [2]
> - !Screenshot from 2019-09-10 15-27-22.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Description:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x)
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
was:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern)
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x)
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Description:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
[2]
-
was:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x)
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns (from accumulate, free form drl, pattern) (x) [2]
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> [2]
> -
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Description:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns (from accumulate, free form drl, pattern)
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
was:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns (from accumulate, free form drl, pattern)
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4495) GDST to XLS export: Work item, Metadata and complex condition column support
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4495?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4495:
--------------------------------
Description:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter (/)
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
was:
h2. Acceptance criteria
- Export multiple work item columns, boolean, string, number parameter
- Export multiple metadata columns (/)
- Export multiple retract columns (x) see pictures [1]
- Export multiple BRL condition columns
[1]
- !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
- !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
> GDST to XLS export: Work item, Metadata and complex condition column support
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4495
> URL: https://issues.jboss.org/browse/DROOLS-4495
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-09-10 14-48-40.png, Screenshot from 2019-09-10 14-49-01.png
>
>
> h2. Acceptance criteria
> - Export multiple work item columns, boolean, string, number parameter (/)
> - Export multiple metadata columns (/)
> - Export multiple retract columns (x) see pictures [1]
> - Export multiple BRL condition columns
> [1]
> - !Screenshot from 2019-09-10 14-48-40.png|thumbnail!
> - !Screenshot from 2019-09-10 14-49-01.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFWIP-193) Is updating Kubernetes objects created by Operator supported?
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-193?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFWIP-193:
-------------------------------
Description:
Technically it is possible to update Kubernetes objects which were created by Operator, e.g. StatefulSet, Pods, ...
- Operator has its limitation compared to non-Operator approach (ports, volume mounts, deployment strategy, ...) So user may be tempted to tweak internal objects manually
- But some values of internal objects are automatically synced with Operator (env,..). So even changed they are overwritten by original operator values after a while.
What will be our general recommendation to users:
- Dont touch internal objects?
- We will document what can't be touched?
- We will document what can be touched?
was:
echnically it is possible to update Kubernetes objects which were created by Operator, e.g. StatefulSet, Pods, ...
- Operator has its limitation compared to non-Operator approach (ports, volume mounts, deployment strategy, ...) So user may be tempted to tweak internal objects manually
- But some values of internal objects are automatically synced with Operator (env,..). So even changed they are overwritten by original operator values after a while.
What will be our general recommendation to users:
- Dont touch internal objects?
- We will document what can't be touched?
- We will document what can be touched?
> Is updating Kubernetes objects created by Operator supported?
> -------------------------------------------------------------
>
> Key: WFWIP-193
> URL: https://issues.jboss.org/browse/WFWIP-193
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Technically it is possible to update Kubernetes objects which were created by Operator, e.g. StatefulSet, Pods, ...
> - Operator has its limitation compared to non-Operator approach (ports, volume mounts, deployment strategy, ...) So user may be tempted to tweak internal objects manually
> - But some values of internal objects are automatically synced with Operator (env,..). So even changed they are overwritten by original operator values after a while.
> What will be our general recommendation to users:
> - Dont touch internal objects?
> - We will document what can't be touched?
> - We will document what can be touched?
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFWIP-193) Is updating Kubernetes objects created by Operator supported?
by Martin Choma (Jira)
Martin Choma created WFWIP-193:
----------------------------------
Summary: Is updating Kubernetes objects created by Operator supported?
Key: WFWIP-193
URL: https://issues.jboss.org/browse/WFWIP-193
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Jeff Mesnil
echnically it is possible to update Kubernetes objects which were created by Operator, e.g. StatefulSet, Pods, ...
- Operator has its limitation compared to non-Operator approach (ports, volume mounts, deployment strategy, ...) So user may be tempted to tweak internal objects manually
- But some values of internal objects are automatically synced with Operator (env,..). So even changed they are overwritten by original operator values after a while.
What will be our general recommendation to users:
- Dont touch internal objects?
- We will document what can't be touched?
- We will document what can be touched?
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months