[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Ivo Bek (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Ivo Bek commented on DROOLS-2706:
---------------------------------
[~stetson.robinson] did we already agreed on the name for the *Scenario simulation tool*? *Scenario simulator*? *Scenario test simulator*? Other ideas?
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Ivo Bek (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Ivo Bek commented on DROOLS-2706:
---------------------------------
[~uxdlc] [~mstevens1] [~stetson.robinson] Since Scenario Simulation tool won't be used only for rules I would be for naming it in 7.1 *Scenario Simulation Test ( Preview ) *and *Test Scenario* and as you suggest renaming it in 7.2 to *Scenario Simulation Test *and *Test Scenario (Legacy)*.
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10670) servlet galleon-pack domain-interfaces.xml uses wrong interface feature spec
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFLY-10670:
----------------------------------------
Summary: servlet galleon-pack domain-interfaces.xml uses wrong interface feature spec
Key: WFLY-10670
URL: https://issues.jboss.org/browse/WFLY-10670
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
{code:java}
<origin name="org.wildfly.core:wildfly-core-galleon-pack">
<feature-group name="domain-interfaces"/>
<feature spec="interface">
<param name="interface" value="private"/>
</feature>
</origin>
{code}
Should be domain.interface instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years