Organizations - UI enhancements

[mattswann]

ORGANIZATIONS Overview

• [x] Change label 'Available deployments' to 'Available deploy targets'

Table rows

• [x] Remove outline on hover
• [x] Hide system groups by default - see Users as an example

Action Buttons

• [x] Add tooltips to buttons
• [x] Move the Dashboard button to the action button area, replace the copy with SVG
• [x] Add action buttons - Groups > Projects section

Buttons

• [x] Button labels in the project tab are misleading - change the labels to 'Link Notification' and 'Link Group'

Input fields

• [x] Anytime data validation is used for an input field, please describe the required validation. For example, adding a new group only accepts lowercase, number and '-'

• [x] Adding a new email notification is bugged, there appears to be no validation

• [x] If there is pre-existing information available please add it to the field. For example, when changing a users role allow the existing role to appear as selected.

Placeholder Text

• [x] Change placeholder when adding a new notification to 'Make a selection'

• [x] Change placeholder when adding a project branch to 'Enter branch name'

• [x] Add info icon and hover-over with the following copy 'When using an SSH git URL make sure that you copy the full path and have permission to add a deploy key and webhook. Public repositories can also be used.'

Linking in a Project

• [x] When linking a group or notification IF there is no existing group or notification add a selection to create one. This would trigger the same modal that exists to create only there is an option to 'Add to current project' before confirming the create action.

LAGOON DASHBOARD

• [x] Change placeholder when adding a new environment branch to 'Enter branch name'

Supporting Files Figma Link --> https://www.figma.com/file/XLrZn1fEfEeEkDICLH9QbX/Lagoon---Orgs-UI-updates?type=design&node-id=0%3A1&mode=design&t=xYWfNBU2ChRmeyZt-1

Reference Images

[shreddedbacon]

When linking a group or notification IF there is no existing group or notification add a selection to create one. This would trigger the same modal that exists to create only there is an option to 'Add to current project' before confirming the create action.

I wouldn't do this, I would direct the user to the notifications page in the UI. Having it create the notification in the projects scope could give a false impression that this notification is only for this project, when currently, notifications are not scoped like this.

Notifications are scoped in a one to many relationship, where one notification can be assigned to many projects.

This also means that the Edit (pencil) button of a notification in the project page should either be removed, or link to the organizations notification management page. As again, it could give a false impression it is being edited for that project only

[CGoodwin90]

When linking a group or notification IF there is no existing group or notification add a selection to create one. This would trigger the same modal that exists to create only there is an option to 'Add to current project' before confirming the create action.

I wouldn't do this, I would direct the user to the notifications page in the UI. Having it create the notification in the projects scope could give a false impression that this notification is only for this project, when currently, notifications are not scoped like this.

Notifications are scoped in a one to many relationship, where one notification can be assigned to many projects.

This also means that the Edit (pencil) button of a notification in the project page should either be removed, or link to the organizations notification management page. As again, it could give a false impression it is being edited for that project only

@DaveDarsa got an existing PR for this, the edit button links to the notifications page. Can build on this if required.

[DaveDarsa]

When linking a group or notification IF there is no existing group or notification add a selection to create one. This would trigger the same modal that exists to create only there is an option to 'Add to current project' before confirming the create action.

I wouldn't do this, I would direct the user to the notifications page in the UI. Having it create the notification in the projects scope could give a false impression that this notification is only for this project, when currently, notifications are not scoped like this. Notifications are scoped in a one to many relationship, where one notification can be assigned to many projects. This also means that the Edit (pencil) button of a notification in the project page should either be removed, or link to the organizations notification management page. As again, it could give a false impression it is being edited for that project only

@DaveDarsa got an existing PR for this, the edit button links to the notifications page. Can build on this if required.

awesome @CGoodwin90 - could you merge it into #189 as all the changes mentioned in this issue are there

[DaveDarsa]

All of the mentioned issues fixed in #189