April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-670) include critical test case for Jaeger

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-670?page=com.atlassian.jira.plugin.... ] Prachi Yadav commented on SWSQE-670: ------------------------------------ Hello, Do we have any update on this? > include critical test case for Jaeger > ------------------------------------- > > Key: SWSQE-670 > URL: https://issues.jboss.org/browse/SWSQE-670 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > > Include critical test cases in Jaeger testing -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-670) include critical test case for Jaeger

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-670?page=com.atlassian.jira.plugin.... ] Prachi Yadav reassigned SWSQE-670: ---------------------------------- Assignee: Jeeva Kandasamy (was: Prachi Yadav) > include critical test case for Jaeger > ------------------------------------- > > Key: SWSQE-670 > URL: https://issues.jboss.org/browse/SWSQE-670 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > > Include critical test cases in Jaeger testing -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ] Prachi Yadav updated SWSQE-667: ------------------------------- Attachment: Screenshot from 2019-04-16 18-19-46.png > Checklist for custom fields in order to support existing and future workflows for Jaeger > ---------------------------------------------------------------------------------------- > > Key: SWSQE-667 > URL: https://issues.jboss.org/browse/SWSQE-667 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > Attachments: Screenshot from 2019-04-16 18-19-46.png > > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ] Prachi Yadav commented on SWSQE-667: ------------------------------------ keeping this project as resolved as we get the Jaeger project on JIRA dashboard of tableau. > Checklist for custom fields in order to support existing and future workflows for Jaeger > ---------------------------------------------------------------------------------------- > > Key: SWSQE-667 > URL: https://issues.jboss.org/browse/SWSQE-667 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3439: -------------------------------------- [~gabriolo], this task is not really a blocker or something we *must* have. This is only a suggestion for improvement. If you disagree with the proposal, we don't have to implement this; everything will work just fine even without these changes. Here are my answers to your questions: # Yes, exactly; if the user clicks on an unselectable cell when nothing was selected before, nothing should be selected. If a different cell was selected before, the originally selected cell should stay selected. # Yes, if you use arrow keys to move to an unselectable cell, nothing should change (the previously selected cell should stay selected). This means that the table will have "borders" (cells that can be selected) and you cannot move outside the borders. Currently, the border is the whole table. # It shouldn't be possible to "lose" your cursor; either a selectable cell is selected, or nothing is selected (just like it works now). # No, I think we should change the default behavior; a first selectable cell should be selected by default: this would either be the scenario description of the first row or the INSTANCE 1 (based on what we decide). Basically, this shouldn't introduce any major changes. Currently, the "selection borders" are at the same time the table borders. What I'm proposing is to only change the selection borders a little bit _inside_ the table. > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3439: --------------------------------- Priority: Optional (was: Major) > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Optional > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3892: -------------------------------------- Description: Usability: Reduce the number of clicks / actions to add a nested element. Solution description: When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH was:Usability: Reduce the number of clicks / actions to add a nested element. > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. > Solution description: > When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3892: -------------------------------------- Description: Usability enhancement request: Reduce the number of clicks / actions to add a nested element. Solution description: When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH was: Usability: Reduce the number of clicks / actions to add a nested element. Solution description: When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability enhancement request: Reduce the number of clicks / actions to add a nested element. > Solution description: > When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3892: -------------------------------------- Labels: drools-tools (was: UX UXTeam drools-tools) > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3892: -------------------------------------- Story Points: (was: 2) > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 April 2019