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

Folders for Servers #21

Open
1 task done
SirOMGitsYOU opened this issue Oct 1, 2024 · 3 comments
Open
1 task done

Folders for Servers #21

SirOMGitsYOU opened this issue Oct 1, 2024 · 3 comments
Assignees
Labels
category: suggestion New feature or request priority: P3 Minor Issue: Does not hinder core functionality but may cause slight inconvenience.
Milestone

Comments

@SirOMGitsYOU
Copy link

Is there an existing suggestion for this?

  • I have searched the existing issues before opening this suggestion.

Describe your suggestion

Being able to tag or drag servers into folders would help for those of us that run everything through ptero and would love some organisation!

Describe the solution you'd like

The ability to either drag servers ontop of each other to create a server group / folder or the ability to tag new servers with a folder and these appear at the top of the servers page

Additional context

No response

@SirOMGitsYOU SirOMGitsYOU added category: suggestion New feature or request needs triage This issue needs to be reviewed labels Oct 1, 2024
@github-project-automation github-project-automation bot moved this to To triage in Nova Oct 1, 2024
@itsvic-dev itsvic-dev self-assigned this Oct 1, 2024
@itsvic-dev itsvic-dev moved this from To triage to Backlog in Nova Oct 1, 2024
@itsvic-dev itsvic-dev added priority: P3 Minor Issue: Does not hinder core functionality but may cause slight inconvenience. and removed needs triage This issue needs to be reviewed labels Oct 1, 2024
@am5z
Copy link

am5z commented Oct 14, 2024

banger idea this is

@itsvic-dev itsvic-dev added this to the Nova 1.4.0 milestone Oct 24, 2024
@am5z
Copy link

am5z commented Oct 26, 2024

why not 1.3.0

@SirOMGitsYOU
Copy link
Author

why not 1.3.0

Probably time constraints but hey I’m just grateful it’s being considered full stop. Looking forward to 1.4.0!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: suggestion New feature or request priority: P3 Minor Issue: Does not hinder core functionality but may cause slight inconvenience.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants