[JBoss JIRA] (SWSQE-668) Checklist for custom fields in order to support existing and future workflows for Istio
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-668?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-668:
----------------------------------
Sprint: Kiali Sprint #22 (was: Kiali Sprint #21)
> Checklist for custom fields in order to support existing and future workflows for Istio
> ---------------------------------------------------------------------------------------
>
> Key: SWSQE-668
> URL: https://issues.jboss.org/browse/SWSQE-668
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Prachi Yadav
> Assignee: Yuanlin Xu
> 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)
5 years, 4 months
[JBoss JIRA] (SWSQE-667) Checklist for custom fields in order to support existing and future workflows for Jaeger
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-667?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-667:
----------------------------------
Sprint: Kiali Sprint #22 (was: Kiali Sprint #21)
> 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)
5 years, 4 months
[JBoss JIRA] (SWSQE-723) Be ready for Day2 testing
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-723?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-723:
----------------------------------
Sprint: Kiali Sprint #22 (was: Kiali Sprint #21)
> Be ready for Day2 testing
> -------------------------
>
> Key: SWSQE-723
> URL: https://issues.jboss.org/browse/SWSQE-723
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Priority: Major
> Labels: infrastructure
>
> When Service Mesh GA will be happen,
> there is always a risk to have a Day2 testing of customer scenarios which failed on GA.
> Action Item:
> Have booked a baremetal servers (bladecenter, PSI, beaker... whatever) with OCP 4.1 installed.
> So when an issue happens on customer side, we can rapidly reproduce that and cooperate with dev on fixing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (SWSQE-695) Map Jira Workflows To Tablue Graphs
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-695?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-695:
----------------------------------
Sprint: Kiali Sprint #22 (was: Kiali Sprint #21)
> Map Jira Workflows To Tablue Graphs
> -----------------------------------
>
> Key: SWSQE-695
> URL: https://issues.jboss.org/browse/SWSQE-695
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> Two parts to this task:
> 1) Because only a couple team members have access to Tablue, generate Kiali metric graphs in Tablue and Paste them into a team accessablel doc so that we can analyze these metrics
> 2) Map Jira Workflow queries to Tablue graphs, so that we can better understand how each of the Tablue graphs are generated.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (SWSQE-722) MaistraIstio project role request for Sunil/Prachi to work on Polarion PQI reports
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-722?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-722:
----------------------------------
Sprint: Kiali Sprint #22 (was: Kiali Sprint #21)
> MaistraIstio project role request for Sunil/Prachi to work on Polarion PQI reports
> ----------------------------------------------------------------------------------
>
> Key: SWSQE-722
> URL: https://issues.jboss.org/browse/SWSQE-722
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Sunil Kondkar
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> At present Sunil has read only access for MaistraIstio project.
> Below roles may be needed for the polarion project - MaistraIstio for Sunil and Prachi to be able to work on PQI reports for polarion.
> project_admin, project_user, project_approver, project_assignable, project_qe, project_useradmin
> Todo: Prachi to request through email to the person who created the polarion MaistraIstio project.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
by Ronald Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ]
Ronald Sigal commented on WFLY-11956:
-------------------------------------
Santiago Pericas-Geertsen agreed that it's worth mentioning @PostConstruct in the context of validation, and I've just created JAX-RS issue https://github.com/eclipse-ee4j/jaxrs-api/issues/759 "Clarify role of @PostConstruct annotated methods in validation steps".
> @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11956
> URL: https://issues.jboss.org/browse/WFLY-11956
> Project: WildFly
> Issue Type: Bug
> Components: Bean Validation, REST
> Affects Versions: 16.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Ronald Sigal
> Priority: Major
> Attachments: logging.txt, playground.zip
>
>
> Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_:
> {code}
> @Path("/validated")
> public interface ValidatedJaxRsInterface {
>
> @GET
> @Valid
> @Produces(MediaType.APPLICATION_JSON)
> GreetingModel getHelloGreeting();
> }
> {code}
> will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed.
> This can be reproduced with the attached reproducer application...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months