[JBoss JIRA] (SWSQE-825) OCP on PSI Cluster - New non admin user by default
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-825?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-825:
-------------------------------------
jenkins user must have cluster-admin role as it is a user which should be used for wider configuration before tests (kubeadmin is not disabled but we don't store it's generated password by installer anywhere)
I can't use kiali and kiali-viewer roles at cluster installation time but those could be used later after kiali installation.
So I would suggest to use existing users jenkins2, foo and foo2 for testing and set roles required by given test in before test method using jenkins user which has cluster-admin role.
> OCP on PSI Cluster - New non admin user by default
> --------------------------------------------------
>
> Key: SWSQE-825
> URL: https://issues.jboss.org/browse/SWSQE-825
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> For MultyTenancy testing it is convenient to have a by default created non admin user "foo/foo" (or other credentials) on OCP clusters provided from PSI.
> By default this user should not have view access to any namespace.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[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: example.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: example.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, 12 months
[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: example-visual.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: example.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, 12 months
[JBoss JIRA] (SWSQE-825) OCP on PSI Cluster - New non admin user by default
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-825?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-825:
-----------------------------------------------
Just FYI
kiali and kiali-viewer are the names that kiali roles created by kiali when kiali is running on MT mode.
> OCP on PSI Cluster - New non admin user by default
> --------------------------------------------------
>
> Key: SWSQE-825
> URL: https://issues.jboss.org/browse/SWSQE-825
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> For MultyTenancy testing it is convenient to have a by default created non admin user "foo/foo" (or other credentials) on OCP clusters provided from PSI.
> By default this user should not have view access to any namespace.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months