github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Restrict permissions on Milestones #3894

New Issue
Open
opened 2025-11-02 05:29:49 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:29:49 -06:00
Owner
Copy Link

Originally created by @mbarinc on GitHub (Sep 4, 2019).

  • Gitea version (or commit ref): 1.10.0+dev-145
  • Git version: 2.20
  • Operating system: RedHat 7.3
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Now, every users can create / modify / delete milestones.
It's possible to block these actions on specific team?

It would be useful if only teams with a specific flag can be able to manage the milestones (for example under the Issue section in the edit team page, like the screenshot below)

Screenshots

image

Originally created by @mbarinc on GitHub (Sep 4, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.10.0+dev-145 - Git version: 2.20 - Operating system: RedHat 7.3 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Now, every users can create / modify / delete milestones. It's possible to block these actions on specific team? It would be useful if only teams with a specific flag can be able to manage the milestones (for example under the Issue section in the edit team page, like the screenshot below) ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![image](https://user-images.githubusercontent.com/3716953/64260456-2f8fb000-cf2b-11e9-88b5-ad3835688da4.png)
GiteaMirror added the type/proposal label 2025-11-02 05:29:49 -06:00
GiteaMirror commented 2025-11-02 05:29:49 -06:00
Author
Owner
Copy Link

@mbarinc commented on GitHub (Sep 5, 2019):

For my purpouse, I have modified the following lines in milestone.tmpl, removing CanWriteIssues and CanWritePulls with IsRepositoryOwner.
In this way only people joined in owner group can modify / delete the milestones:

85f56546c4/templates/repo/issue/milestones.tmpl (L70)

85f56546c4/templates/repo/issue/milestones.tmpl (L94)

I think that is correct that only some users can manage the milestones.

@mbarinc commented on GitHub (Sep 5, 2019): For my purpouse, I have modified the following lines in milestone.tmpl, removing CanWriteIssues and CanWritePulls with IsRepositoryOwner. In this way only people joined in owner group can modify / delete the milestones: https://github.com/go-gitea/gitea/blob/85f56546c4259ed9c11d31973344228ad667084e/templates/repo/issue/milestones.tmpl#L70 https://github.com/go-gitea/gitea/blob/85f56546c4259ed9c11d31973344228ad667084e/templates/repo/issue/milestones.tmpl#L94 I think that is correct that only some users can manage the milestones.
GiteaMirror commented 2025-11-02 05:29:50 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 23, 2019):

We need a new unit named milestone to do that.

@lunny commented on GitHub (Dec 23, 2019): We need a new unit named `milestone` to do that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3894
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?