August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10913) CodecSessionConfig#findSessionId() causes an incorrect JSESSIONID Set-Cookie header

by Masafumi Miura (JIRA)

Masafumi Miura created WFLY-10913: ------------------------------------- Summary: CodecSessionConfig#findSessionId() causes an incorrect JSESSIONID Set-Cookie header Key: WFLY-10913 URL: https://issues.jboss.org/browse/WFLY-10913 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 13.0.0.Final, 14.0.0.Beta2 Reporter: Masafumi Miura Assignee: Stuart Douglas This issue is very similar to WFLY-10262/JBEAP-14641 but the condition causing the problem is a bit different. The issue happens when the client sends JSESSIONID Cookie in the request to the web application does NOT use HttpSession. JSESSIONID Set-Cookie response header should not be sent in this scenario, but WildFly/EAP 7 returns the response with JSESSIONID reusing the requested session id which does not exist in the session manager. The fix for WFLY-10262 / JBEAP-14641 added AttachmentKey SESSION_ID_SET to avoid invoking CodecSessionConfig#setSessionId() more than once. However, the fix does not help for this issue because CodecSessionConfig#setSessionId() is not invoked (= SESSION_ID_SET is null) before the problematic CodecSessionConfig#findSessionId() processing in this scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10912) CodecSessionConfig#findSessionId() causes an incorrect JSESSIONID Set-Cookie header

by Masafumi Miura (JIRA)

Masafumi Miura created WFLY-10912: ------------------------------------- Summary: CodecSessionConfig#findSessionId() causes an incorrect JSESSIONID Set-Cookie header Key: WFLY-10912 URL: https://issues.jboss.org/browse/WFLY-10912 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 14.0.0.Beta2, 13.0.0.Final Reporter: Masafumi Miura Assignee: Stuart Douglas This issue is very similar to WFLY-10262/JBEAP-14641 but the condition causing the problem is a bit different. The issue happens when the client sends JSESSIONID Cookie in the request to the web application does NOT use HttpSession. JSESSIONID Set-Cookie response header should not be sent in this scenario, but WildFly/EAP 7 returns the response with JSESSIONID reusing the requested session id which does not exist in the session manager. The fix for WFLY-10262 / JBEAP-14641 added AttachmentKey SESSION_ID_SET to avoid invoking CodecSessionConfig#setSessionId() more than once. However, the fix does not help for this issue because CodecSessionConfig#setSessionId() is not invoked (= SESSION_ID_SET is null) before the problematic CodecSessionConfig#findSessionId() processing in this scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10876) Align jar file provided for MP OpenTracing into right modules

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10876?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10876: -------------------------------------- I've figured it out. I'm not sure if it's the best solution or not, but essentially the {{io.smallrye.opentracing}} module needs a dependency on {{org.wildfly.microprofile.opentracing-smallrye}} since that's where the extension lives. This does create a circular dependency which could be a little weird, but seems to work. I'll submit a PR soon for further discussion. > Align jar file provided for MP OpenTracing into right modules > ------------------------------------------------------------- > > Key: WFLY-10876 > URL: https://issues.jboss.org/browse/WFLY-10876 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Juraci Paixão Kröhling > Priority: Critical > > With recent addition of MicroProfile OpenTracing implementation we currently have following set of jar files that are in the build to provide various MicroProfile features: > {code} > $ find modules | grep smallrye | grep jar$ | xargs ls -hl > -rw-rw-r--. 1 jstourac jstourac 39K Aug 16 15:13 modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > -rw-rw-r--. 1 jstourac jstourac 8.9K Aug 16 15:13 modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > -rw-rw-r--. 1 jstourac jstourac 38K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 27K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 228K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/gson-2.8.2.jar > -rw-rw-r--. 1 jstourac jstourac 123K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-core-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 2.8M Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 14K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.5K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 41K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > -rw-rw-r--. 1 jstourac jstourac 7.9K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 13K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 5.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/smallrye-opentracing-1.1.1.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > {code} > It looks like the opentracing-smallrye module could be split up into a few separate modules. There at least two motivations: > # particular implementation into its own module separate from the e.g. microprofile specification > # because of the way how current patching mechanism works in WildFly, if we leave current {{opentracing-smallrye}} module as is, in case of a one-off patch it would mean to replace all files in the module - currently 3.3MB: > {code} > $ du -h modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > 3.3M modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > {code} > My proposal how to align the jar files is following: > # jaeger specific files should go into separate jaeger module > # {{wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar}} should be moved to new {{modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye}} module so it matches what is done for {{health-smallrye}} and {{config-smallrye}} in extension subdir > # {{smallrye-opentracing-1.1.1.jar}} should be moved to {{base/io}} as is done for {{config}} and {{health}} - {{modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar}} > # what about that {{gson-2.8.2.jar}} dependency? Shall it be moved to some more generic place? > This would give us following structure: > {code} > modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > ---- I have no idea how this module for jaeger should be named... > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-core-0.30.4.jar > ---- I have no idea how this module for gson should be named... > modules/system/layers/base/org/wildfly/gson/main/gson-2.8.2.jar > {code} > One additional piece for consideration - maybe we should also split up jar files that are just the microprofile-opentracing specification (api at least I guess) apart from the others in the {{modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/}} > What do you think? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10876) Align jar file provided for MP OpenTracing into right modules

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10876?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-10876: ------------------------------------ Assignee: James Perkins (was: Juraci Paixão Kröhling) > Align jar file provided for MP OpenTracing into right modules > ------------------------------------------------------------- > > Key: WFLY-10876 > URL: https://issues.jboss.org/browse/WFLY-10876 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: James Perkins > Priority: Critical > > With recent addition of MicroProfile OpenTracing implementation we currently have following set of jar files that are in the build to provide various MicroProfile features: > {code} > $ find modules | grep smallrye | grep jar$ | xargs ls -hl > -rw-rw-r--. 1 jstourac jstourac 39K Aug 16 15:13 modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > -rw-rw-r--. 1 jstourac jstourac 8.9K Aug 16 15:13 modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > -rw-rw-r--. 1 jstourac jstourac 38K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 27K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 228K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/gson-2.8.2.jar > -rw-rw-r--. 1 jstourac jstourac 123K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-core-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 2.8M Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 14K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.5K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 41K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > -rw-rw-r--. 1 jstourac jstourac 7.9K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 13K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 5.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/smallrye-opentracing-1.1.1.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > {code} > It looks like the opentracing-smallrye module could be split up into a few separate modules. There at least two motivations: > # particular implementation into its own module separate from the e.g. microprofile specification > # because of the way how current patching mechanism works in WildFly, if we leave current {{opentracing-smallrye}} module as is, in case of a one-off patch it would mean to replace all files in the module - currently 3.3MB: > {code} > $ du -h modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > 3.3M modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > {code} > My proposal how to align the jar files is following: > # jaeger specific files should go into separate jaeger module > # {{wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar}} should be moved to new {{modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye}} module so it matches what is done for {{health-smallrye}} and {{config-smallrye}} in extension subdir > # {{smallrye-opentracing-1.1.1.jar}} should be moved to {{base/io}} as is done for {{config}} and {{health}} - {{modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar}} > # what about that {{gson-2.8.2.jar}} dependency? Shall it be moved to some more generic place? > This would give us following structure: > {code} > modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > ---- I have no idea how this module for jaeger should be named... > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-core-0.30.4.jar > ---- I have no idea how this module for gson should be named... > modules/system/layers/base/org/wildfly/gson/main/gson-2.8.2.jar > {code} > One additional piece for consideration - maybe we should also split up jar files that are just the microprofile-opentracing specification (api at least I guess) apart from the others in the {{modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/}} > What do you think? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-385) Kiali-Test-Meshes-Ansible Failure

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-385?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-385. ------------------------------------------- Resolution: Done > Kiali-Test-Meshes-Ansible Failure > --------------------------------- > > Key: SWSQE-385 > URL: https://issues.jboss.org/browse/SWSQE-385 > Project: Kiali QE > Issue Type: Bug > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > > Hi Guilherme, > Please take a look into this failure, it started happening today: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Test-Meshe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-373) Adjust pipeline to install Maistra (Istio Downstream) 1.0

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-373?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-373. ------------------------------------------- Resolution: Done > Adjust pipeline to install Maistra (Istio Downstream) 1.0 > --------------------------------------------------------- > > Key: SWSQE-373 > URL: https://issues.jboss.org/browse/SWSQE-373 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > - Move from https://github.com/openshift-istio/openshift-ansible to https://github.com/Maistra/openshift-ansible > - Learn Istio Operator https://github.com/Maistra/istio-operator -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-342) QE: Kiali move to Istio 1.0.0

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-342?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-342. ------------------------------------------- Resolution: Done > QE: Kiali move to Istio 1.0.0 > ----------------------------- > > Key: SWSQE-342 > URL: https://issues.jboss.org/browse/SWSQE-342 > Project: Kiali QE > Issue Type: Story > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > > Kiali is going to be moved on Istio 1.0.0, dev branch is created for that. > Early testing was completed from QE side. > We need several tasks on QE side to adjust Pipeline, Bookinfo installation, checker job... > This is umbrella task for Istio 1.0.0 moving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2921) [DMN Designer] Stack overflow when a Context has two Relations

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2921?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2921: ----------------------------------- Story Points: 8 Sprint: 2018 Week 36-38 > [DMN Designer] Stack overflow when a Context has two Relations > -------------------------------------------------------------- > > Key: DROOLS-2921 > URL: https://issues.jboss.org/browse/DROOLS-2921 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > Create a {{Context}} with two {{ContextEntries}}. Set both to be a {{Relation}}. Stack overflow :-( > You can have multiple {{Relation}} in different {{Contexts}} it only happens when within the same {{Context}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2874: ---------------------------------------- [~uxdlc] I commented on Slack, the "data type selector" uses PatternFly's https://www.patternfly.org/pattern-library/widgets/#bootstrap-select that uses https://developer.snapappointments.com/bootstrap-select/examples/#live-se.... We can make your popover in general; but if you want to make the "data type selector" look different etc we may be more limited as we're simply re-using a third party library widget. > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2874: ------------------------------------- [~manstis] Thanks much, have pinged Edson. > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 August 2018