Use full path for security policy scope project selector
Why are we doing this work
Relevant links
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
-
use fullPath using patch below
Patch
diff --git a/ee/app/assets/javascripts/security_orchestration/components/group_projects_dropdown.vue b/ee/app/assets/javascripts/security_orchestration/components/group_projects_dropdown.vue
index f8f29b2c5361..fd2f01d9c710 100644
--- a/ee/app/assets/javascripts/security_orchestration/components/group_projects_dropdown.vue
+++ b/ee/app/assets/javascripts/security_orchestration/components/group_projects_dropdown.vue
@@ -101,13 +101,13 @@ export default {
return this.projectsPageInfo.hasNextPage;
},
projectItems() {
- return this.projects?.reduce((acc, { id, name }) => {
- acc[id] = name;
+ return this.projects?.reduce((acc, { id, fullPath }) => {
+ acc[id] = fullPath;
return acc;
}, {});
},
projectListBoxItems() {
- return this.projects.map(({ id, name }) => ({ text: name, value: id }));
+ return this.projects.map(({ id, fullPath }) => ({ text: fullPath, value: id }));
},
projectsIds() {
return this.projects.map(({ id }) => id);
-
fix styling for long path names -
limit dropdown size -
truncate and add tooltip
-
Verification steps
Edited by Alexander Turinske