-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Proposal: Pin Issues #2175
Comments
This could be implemented by a default label like |
Adding Issue Priority and being able to sort on that would make more sense to me. Anyone else? |
@bkcsoft Yes, a priority in database column, but we could also has a button to pin it. |
@daviian Yes. I mean, we only need to add one column order by `priority` desc, ... When you |
@lunny i like the idea. Also priority would be a cool feature 😀 (but wouldn't this be a seperate issue?) |
I've been working on it :) |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Implementing these 2 features with a single additional column may be more optimal, but this way on unpinning the priority cannot be restored to its old value. |
Why not use wiki for that? |
This adds the ability to pin important Issues and Pull Requests. You can also move pinned Issues around to change their Position. Resolves #2175. ## Screenshots ![grafik](https://user-images.githubusercontent.com/15185051/235123207-0aa39869-bb48-45c3-abe2-ba1e836046ec.png) ![grafik](https://user-images.githubusercontent.com/15185051/235123297-152a16ea-a857-451d-9a42-61f2cd54dd75.png) ![grafik](https://user-images.githubusercontent.com/15185051/235640782-cbfe25ec-6254-479a-a3de-133e585d7a2d.png) The Design was mostly copied from the Projects Board. ## Implementation This uses a new `pin_order` Column in the `issue` table. If the value is set to 0, the Issue is not pinned. If it's set to a bigger value, the value is the Position. 1 means it's the first pinned Issue, 2 means it's the second one etc. This is dived into Issues and Pull requests for each Repo. ## TODO - [x] You can currently pin as many Issues as you want. Maybe we should add a Limit, which is configurable. GitHub uses 3, but I prefer 6, as this is better for bigger Projects, but I'm open for suggestions. - [x] Pin and Unpin events need to be added to the Issue history. - [x] Tests - [x] Migration **The feature itself is currently fully working, so tester who may find weird edge cases are very welcome!** --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: Giteabot <teabot@gitea.io>
I don't know if this is overkill or if there is a better solution, but i'd like to have the abililty to pin issues to have them sticking at the top of the issues page.
This could be useful for general information you don't want to put in the readme or issues everyone in the team should comment.
More Context:
I'm currently working on a project with a bunch of other people. We don't know each other, so someone opened an "introduce yourself"-issue. But now we have so many issues that this one is already on the second page, so noone recognizes it anymore and until now, only two people introduced themselves.
The text was updated successfully, but these errors were encountered: