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

Add type filter to System Notices view #11909

Closed
wants to merge 6 commits into from

Conversation

a1012112796
Copy link
Member

@a1012112796 a1012112796 commented Jun 16, 2020

After #10745 was merged, the number of System Notices increased obviously.
Add the type filter is useful to help users to quickly check out the useful message they want.

view:
image

After go-gitea#10745 was merged, the number of System Notices increased obviously.
Add the type filter is useful to help users to quickly check out the useful
message they want.

Signed-off-by: a1012112796 <1012112796@qq.com>
@techknowlogick techknowlogick added type/enhancement An improvement of existing functionality topic/ui Change the appearance of the Gitea UI labels Jun 16, 2020
@techknowlogick techknowlogick added this to the 1.13.0 milestone Jun 16, 2020
@6543
Copy link
Member

6543 commented Jun 16, 2020

can you add a smal screenshot?

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jun 16, 2020
@a1012112796
Copy link
Member Author

can you add a smal screenshot?

ok

@lunny
Copy link
Member

lunny commented Jun 17, 2020

How about move the filter to right?

models/admin.go Outdated Show resolved Hide resolved
models/admin.go Outdated Show resolved Hide resolved
models/admin.go Outdated Show resolved Hide resolved
@@ -20,8 +20,10 @@ type NoticeType int
const (
//NoticeRepository type
NoticeRepository NoticeType = iota + 1
// NoticeTask type
NoticeTask
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like we have a new column named status but not put all in type

Copy link
Member Author

@a1012112796 a1012112796 Jun 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm not sure whether it's a good idea because it will result in big changs and it's not usefull for NoticeRepository now. 🤔

@stale
Copy link

stale bot commented Aug 21, 2020

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions.

@stale stale bot added the issue/stale label Aug 21, 2020
@SuperSandro2000
Copy link
Contributor

Bump

@stale stale bot removed the issue/stale label Aug 21, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Aug 24, 2020
@lunny lunny modified the milestones: 1.13.0, 1.14.0 Sep 9, 2020
@6543
Copy link
Member

6543 commented Dec 8, 2020

updates?

@a1012112796
Copy link
Member Author

updates?

Hmm, I think this pull requst is not so necessary now. because we can disable success task message by config file now.

@a1012112796 a1012112796 closed this Jan 3, 2021
@a1012112796 a1012112796 deleted the notice_ui branch January 3, 2021 14:57
@a1012112796 a1012112796 removed this from the 1.14.0 milestone Jan 3, 2021
@6543
Copy link
Member

6543 commented Jan 3, 2021

I think we should be able to filter, more specific: why not add a search-box to filter by keywords?

created #14228

@go-gitea go-gitea locked and limited conversation to collaborators Feb 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. topic/ui Change the appearance of the Gitea UI type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants