Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cloud provider selection reason (Text field) for Public Cloud #3636

Closed
ThibaultBC opened this issue Aug 29, 2024 · 13 comments
Closed

Add Cloud provider selection reason (Text field) for Public Cloud #3636

ThibaultBC opened this issue Aug 29, 2024 · 13 comments
Assignees

Comments

@ThibaultBC
Copy link

ThibaultBC commented Aug 29, 2024

As a Platform Administrator, I want to track reasons that lead to a cloud service provider selection, so that I can report on those reasons for procurement requirements and also feed data to our service design research.

ADDITIONAL Requirements:
Please see the comments below.

Acceptance Criteria:

  1. On the Product Registry, when provisioning a new project, or editing an existing one, add a "Cloud provider selection" section just below/after the "Cloud service provider" dropdown section.
  2. This should be a text field, character limit 1000. (similar look and feel as the "Description field above").
  3. Explanation text below: "Please provide a short description of the reason(s) that lead you to select this cloud service provider."
  4. For any new project provisioning, make this field mandatory.
  5. For any existing project, this should be blank, and mandatory to answer when a user comes in and wants to save changes (prompt them to fill out this field).
  6. Add this field to the CSV export.
@ThibaultBC
Copy link
Author

ThibaultBC commented Aug 29, 2024

As a Platform Administrator, I want to track reasons that lead to a cloud service provider selection, so that I can report on those reasons for procurement requirements and also feed data to our service design research.

Acceptance Criteria:

  1. On the Product Registry, when provisioning a new project, or editing an existing one, add a "Cloud provider selection" section just below/after the "Cloud service provider" dropdown section.
  2. This should be a text field, character limit 1000. (similar look and feel as the "Description field above").
  3. Explanation text below: "Please provide a short description of the reason(s) that lead you to select this cloud service provider."
  4. For any new project provisioning, make this field mandatory.
  5. For any existing project, this should be blank, and mandatory to answer when a user comes in and wants to save changes (prompt them to fill out this field).
  6. Add this field to the export.
  7. make it the multiple choice dropdown

@ThibaultBC
Copy link
Author

Note: This is initially required for Public Cloud, but my suggestion is it would also be useful information for Private Cloud projects.

@Iryna-Kaplun Iryna-Kaplun changed the title Cloud provider selection reason - Text field Add Cloud provider selection reason - Text field for Public Cloud Aug 29, 2024
@Iryna-Kaplun Iryna-Kaplun changed the title Add Cloud provider selection reason - Text field for Public Cloud Add Cloud provider selection reason (Text field) for Public Cloud Aug 29, 2024
@Iryna-Kaplun
Copy link
Collaborator

@Kolezhanchik
Copy link
Collaborator

questions:
should this info be shown on product page for users and/or admins
should this info be included in email notifications, nats-messages
add this filed to export - does it mean to add it to eMOU or .csv file with list of products?
answers from Thibault:
No need to display it on the product page
Not sure what's the nats-message, emails notifications: no need to edit the emails with this info.
Export: I meant the CSV export that we can access from the products page (cf. screenshots)

@ThibaultBC
Copy link
Author

Hello,
Following up on a discussion with Olena, we would like to add a dropdown field, in order to make this result more easily extractable for statistics.
This doesn't change the previously laid out acceptance criteria, but there will be an addition to this ticket.

  1. In the "Cloud Provider Selection" section, above the text field, add a dropdown field, with the default option being "Select reason"
  2. Options available in the dropdown list are as follow:
  • Cost Efficiency
  • Scalability Needs
  • Security Level
  • High Availability/Disaster Recovery features
  • Specialized Cloud Services (e.g., AI/ML, Big Data)
  • Vendor Preference
  • My Team Expertise
  • Internal Support Level within OCIO,
  • Project-Specific Requirements
  • Other
  1. Text below the dropdown space "Please select the main reason that led your choice of cloud provider."
  2. Both fields (the dropdown, and the text description) are mandatory.

@golebu2020
Copy link
Collaborator

I guess you're talking about something like this?: image.png

@junminahn
Copy link
Collaborator

junminahn commented Sep 5, 2024

@golebu2020 you can use mantine's multi select component:
https://mantine.dev/core/multi-select/

ex) https://github.com/bcgov/platform-services-registry/blob/main/app/app/team-api-accounts/AccountRoles.tsx#L17

for textarea, please use the textarea from the other pages for now; (we will create a commom component for textarea later)

@golebu2020
Copy link
Collaborator

Okay

@golebu2020
Copy link
Collaborator

golebu2020 commented Sep 5, 2024

@junminahn @Iryna-Kaplun @ThibaultBC is this feature applicable to both private and public cloud registries?

@Kolezhanchik
Copy link
Collaborator

public cloud,(at least for now)

@golebu2020
Copy link
Collaborator

okay

@funtigr
Copy link
Collaborator

funtigr commented Oct 1, 2024

Now we have a new field and dropdown for the reasons of provider selection. Textfield has limit for 1000 characters.
image.png

The CSV has the fields listed:
image.png

@funtigr funtigr closed this as completed Oct 7, 2024
@funtigr
Copy link
Collaborator

funtigr commented Oct 7, 2024

We checked the bug with Cloud provider choice reason with Prabhu.
The issue occurred because the Request was created before the deployment of the feature.
And the attempt to Review it was made after the deployment of the feature.
This way the fields were left empty but were already needed while reviewing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants