mirror of
https://github.com/pelican-dev/plugins.git
synced 2026-05-09 08:26:01 +02:00
[GH-ISSUE #55] [Tickets] Users without role can't create ticket #38
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/plugins#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Fuggschen on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/pelican-dev/plugins/issues/55
If a user has no role (was not needed until now since we created and assigned the servers manually) they can only view their tickets but have no option to create one
@coderabbitai[bot] commented on GitHub (Dec 25, 2025):
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
Examples
🔗 Similar Issues
Possible Duplicates
Related Issues
👤 Suggested Assignees
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
@rmartinoscar commented on GitHub (Dec 25, 2025):
An other case of you can't use the same Policie for admin & client side https://github.com/pelican-dev/panel/issues/1831
@Boy132 commented on GitHub (Dec 25, 2025):
That should've been fixed with
github.com/pelican-dev/plugins@499ffff453.Are you using the latest plugin?
@Fuggschen commented on GitHub (Dec 25, 2025):
I have v1.0.0 and don't see any update and the plugin even in the git says v1.0.0 so probably yes?
@Boy132 commented on GitHub (Dec 25, 2025):
It's always 1.0.0, there currently is no versioning. When did you download the plugin?
Or, if you unsure, download the plugin again.
@Fuggschen commented on GitHub (Dec 25, 2025):
Alr yes, the latest patch did fix it. Haven't catched it because there wasn't any update indicator. Thanks