apache / apache/cloudstack

User Experience: Allow users to add Description to Private Gateway and Static Routes

Ouverte
#8,837 8 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
component:api component:database component:UI good-first-issue type:improvement
Langage dominant
Java
Étoiles
3.1k
Forks
1.4k
Merge moyen
6 j 19 h
PR mergées (30 j)
32

Description

##### ISSUE TYPE

* Enhancement Request

##### COMPONENT NAME

~~~
UI Enhancement
~~~

##### CLOUDSTACK VERSION

~~~
4.19
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

N/A

##### SUMMARY

##### STEPS TO REPRODUCE

Currently, the Cloudstack UI doesnt support users to add descriptions/notes to their created Private Gateways and Static Routes

I propose adding descriptions To Private Gateways and Static Routes because as the number of gateways grows, i lose track of what each gateway was for, which makes it hard to maintain. And a Private Gateway can have many static routes, which are very hard to keep track too.

I see a large list, but i have no idea what each one is for. It becomes even worse if i have a colleague who adds another gateway and i have no i wont be able to identify (cause the list is so long) or understand what the item was created for.

I think this feature is one of those that are low hanging fruits that would greatly improve the users experience.

~~~

~~~

##### EXPECTED RESULTS

~~~
To be able to add descriptions to Private Gateways and Static Routes so its easier to maintain in the long term.
~~~

##### ACTUAL RESULTS

~~~
I add many private gateways and Static Routes without knowing its reference that its becoming very hard to maintain.
~~~

Screenshot 2024-03-26 at 10 32 27 pm

Screenshot 2024-03-26 at 10 46 20 pm

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par les flux UI de Private Gateways et Static Routes décrits dans l’issue #8837 et vérifiez leur comportement actuel sur la version de CloudStack concernée ou dans le main branch. Suivez la manière dont chaque ressource est créée et listée ; c’est terminé lorsque les utilisateurs peuvent saisir des descriptions pour les deux ressources et les voir lors de la maintenance des listes correspondantes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
frontend
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.