What would you like to happen?
The Apache Hop Project Manager is currently very useful and has improved a lot over time. The current experience is already good, especially for managing and activating projects quickly.
This activity is only a suggestion for a possible future improvement.
Today, when there are many projects, the list can become harder to navigate because all projects are displayed together. Since environments already belong inside each project, the proposal is not to organize projects by environment.
The idea is to improve project organization using groups and tags.
Suggested improvement:
Allow projects to be organized into custom groups.
Allow projects to have one or more tags.
Allow filtering by project name, group, or tag.
Keep the current simple list behavior, but add optional organization features for users with many projects.
Example groups:
Clients
Internal Projects
Data Migration Projects
Legacy Projects
Proof of Concept Projects
Example tags:
customer-a
customer-b
etl
data-lake
critical
legacy
active
archived
Expected benefits:
Easier navigation when many projects exist.
Better organization without changing how environments work today.
Faster identification of related projects.
More flexibility than folders only, because a project could have multiple tags.
Keeps the current good experience while adding more options for larger project lists.
This would be an optional enhancement, not a replacement for the current project manager behavior.
Issue Priority
Priority: 3
Issue Component
Component: Hop Gui
What would you like to happen?
The Apache Hop Project Manager is currently very useful and has improved a lot over time. The current experience is already good, especially for managing and activating projects quickly.
This activity is only a suggestion for a possible future improvement.
Today, when there are many projects, the list can become harder to navigate because all projects are displayed together. Since environments already belong inside each project, the proposal is not to organize projects by environment.
The idea is to improve project organization using groups and tags.
Suggested improvement:
Allow projects to be organized into custom groups.
Allow projects to have one or more tags.
Allow filtering by project name, group, or tag.
Keep the current simple list behavior, but add optional organization features for users with many projects.
Example groups:
Clients
Internal Projects
Data Migration Projects
Legacy Projects
Proof of Concept Projects
Example tags:
customer-a
customer-b
etl
data-lake
critical
legacy
active
archived
Expected benefits:
Easier navigation when many projects exist.
Better organization without changing how environments work today.
Faster identification of related projects.
More flexibility than folders only, because a project could have multiple tags.
Keeps the current good experience while adding more options for larger project lists.
This would be an optional enhancement, not a replacement for the current project manager behavior.
Issue Priority
Priority: 3
Issue Component
Component: Hop Gui