July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4205: -------------------------------------- Attachment: (was: mockup.png) > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: overview.png > > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4205: -------------------------------------- Attachment: overview.png > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: overview.png > > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-899) Create plan document

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-899?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-899. --------------------------------- Resolution: Done Doc: > Create plan document > -------------------- > > Key: SWSQE-899 > URL: https://issues.jboss.org/browse/SWSQE-899 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > Which steps we need to take before outage, after outage? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-899) Create plan document

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-899?page=com.atlassian.jira.plugin.... ] Filip Brychta edited comment on SWSQE-899 at 7/31/19 9:02 AM: -------------------------------------------------------------- Doc: https://docs.google.com/document/d/1QRABnGYjgG9J0_QImiMPA78uL8NXmjLJbV864... was (Author: fbrychta): Doc: > Create plan document > -------------------- > > Key: SWSQE-899 > URL: https://issues.jboss.org/browse/SWSQE-899 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > Which steps we need to take before outage, after outage? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-899) Create plan document

by Filip Brychta (Jira)

Filip Brychta created SWSQE-899: ----------------------------------- Summary: Create plan document Key: SWSQE-899 URL: https://issues.jboss.org/browse/SWSQE-899 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Which steps we need to take before outage, after outage? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-898) Prepare for BOS lab outage

by Filip Brychta (Jira)

Filip Brychta created SWSQE-898: ----------------------------------- Summary: Prepare for BOS lab outage Key: SWSQE-898 URL: https://issues.jboss.org/browse/SWSQE-898 Project: Kiali QE Issue Type: Story Reporter: Filip Brychta Assignee: Filip Brychta There is an outage scheduled on Tuesday, August 20th and Wednesday the 21st. This outage will affect jon/kiali qe infrastructure and following systems will not be accessible: - https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/ - http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/ - https://foreman.jonqe.lab.eng.bos.redhat.com - https://rhevm.jonqe.lab.eng.bos.redhat.com - all Dell system b01 -- b25 For JON it means following: - no provisioning via foreman - no jenkins jobs For kiali it means following: - no jenkins jobs (PR testing, nightly testing, provisioning of ocp4 in PSI, ...) - ocp 3.11 clusters in bladecenter will not be available - ocp 4 clusters in PSI will not be affected so manual testing will be possible but automatic provisioning of new cluster will not be available (jenkins will be down) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1858) Create Three new shaded jars elytron-common, elytron-acme, and elytron-password

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1858: ------------------------------------- Summary: Create Three new shaded jars elytron-common, elytron-acme, and elytron-password Key: ELY-1858 URL: https://issues.jboss.org/browse/ELY-1858 Project: WildFly Elytron Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.0.0.Alpha5 These are for use by Quarkus bundling together some of the common dependencies. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-167: ------------------------------------ Isn't this externalizing configuration denying infrastucture immutability concept? So far we have overriding feature in s2i [1], but that keep infrastructure immutability pattern. But current Operator does not have s2i support. Also note as there will be only one Operator at a time, we cant remove StandaloneConfigMapSpec, when s2i will be part of operator. So now question is is it worth adding it in current state? [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... > EAP Operator handling ConfigMap internally > ------------------------------------------ > > Key: WFWIP-167 > URL: https://issues.jboss.org/browse/WFWIP-167 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap. > Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users. > Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me. > However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator. > What do you think? Have you considered this approach? > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4587) Clarify description of 'maximum-cert-path'

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4587?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4587: ---------------------------------------- Assignee: Jan Stourac (was: Darran Lofthouse) > Clarify description of 'maximum-cert-path' > ------------------------------------------ > > Key: WFCORE-4587 > URL: https://issues.jboss.org/browse/WFCORE-4587 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Trivial > Fix For: 10.0.0.Beta3 > > > Trivial extension of 'maximum-cert-path' attribute of trust-manager to give message when this value actually takes any effect - only if OCSP or CRL are configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4587) Clarify description of 'maximum-cert-path'

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4587?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4587: ------------------------------------- Fix Version/s: 10.0.0.Beta3 > Clarify description of 'maximum-cert-path' > ------------------------------------------ > > Key: WFCORE-4587 > URL: https://issues.jboss.org/browse/WFCORE-4587 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Trivial > Fix For: 10.0.0.Beta3 > > > Trivial extension of 'maximum-cert-path' attribute of trust-manager to give message when this value actually takes any effect - only if OCSP or CRL are configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019