[
https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi...
]
Liz Clayton updated DROOLS-2706:
--------------------------------
Description:
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.
was:
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 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.
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)