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

Issue priority #4823

Closed
wants to merge 24 commits into from
Closed

Issue priority #4823

wants to merge 24 commits into from

Conversation

BetaCat0
Copy link
Member

Priority updating api for issues (both web and api).
The build will fail due to this PR.

@lafriks
Copy link
Member

lafriks commented Aug 29, 2018

I would prefer this to be labels based (like assigning label a priority) and priority in db for issue would be calculated as max from all labels when changing issue label(s)

@bkcsoft bkcsoft added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Aug 29, 2018
@lafriks lafriks added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/changelog Adds the changelog for a new Gitea version labels Aug 29, 2018
@lafriks lafriks added this to the 1.7.0 milestone Aug 29, 2018
@lunny
Copy link
Member

lunny commented Aug 30, 2018

@lafriks I think label priority and issue priority are different feature. We need both. I think label priority will not resolve all the things.

@lunny
Copy link
Member

lunny commented Aug 30, 2018

@BetaCat0 but I would like Issue priority not Feature priority. I think higest and lowest should be used in label priority. The issue priority could implement pin issue and unpin issue or you can update the priority value as what you want.

@BetaCat0 BetaCat0 changed the title Feature priority Issue priority Aug 30, 2018
@BetaCat0
Copy link
Member Author

BetaCat0 commented Aug 30, 2018

@lafriks I think label-based priority indicates the displaying sequence of a group of issues with a same label(like JIRA does) . Meanwhile a issue-based priority determine a fixed order in issues query. They don't conflict and they are somekind of two different features just like @lunny said.

@BetaCat0
Copy link
Member Author

@lunny working on it

@BetaCat0 BetaCat0 changed the title Issue priority (WIP) Issue priority Aug 30, 2018
@BetaCat0 BetaCat0 changed the title (WIP) Issue priority WIP Issue priority Aug 30, 2018
@BetaCat0 BetaCat0 changed the title WIP Issue priority Issue priority Aug 30, 2018
HighestPriority
// PriorityDefault defines the default priority
PriorityDefault = 0
// PriorityDefault defines the pinned priority
Copy link
Member

Choose a reason for hiding this comment

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

error comment

routers/api/v1/api.go Outdated Show resolved Hide resolved
routers/api/v1/api.go Outdated Show resolved Hide resolved
models/issue.go Show resolved Hide resolved
@BetaCat0
Copy link
Member Author

Build failed due to this PR

@codecov-io
Copy link

codecov-io commented Sep 1, 2018

Codecov Report

Merging #4823 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #4823   +/-   ##
=======================================
  Coverage   37.35%   37.35%           
=======================================
  Files         308      308           
  Lines       45567    45567           
=======================================
  Hits        17022    17022           
  Misses      26079    26079           
  Partials     2466     2466

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0b6699...300b19e. Read the comment docs.

@BetaCat0
Copy link
Member Author

BetaCat0 commented Sep 1, 2018

Ready for review 😀

@lunny
Copy link
Member

lunny commented Sep 2, 2018

Could you add some screenshot here?

@BetaCat0
Copy link
Member Author

BetaCat0 commented Sep 3, 2018

image

@BetaCat0
Copy link
Member Author

BetaCat0 commented Sep 3, 2018

And you can tap the PIN button to pin/unpin an issue

Copy link
Member

@adelowo adelowo left a comment

Choose a reason for hiding this comment

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

You have files with issus_priority as part of their names ? Shouldn't that be issues_priority or issue_priority ?

models/issus_priority.go Outdated Show resolved Hide resolved
@adelowo
Copy link
Member

adelowo commented Sep 14, 2018

There are merge conflicts @BetaCat0

Signed-off-by: BetaCat0 [email protected]
UpdateIssuePriority is split into two APIs: PinIssue & UnpinIssue

                                            Signed-off-by: BetaCat0 [email protected]
                                            Signed-off-by: BetaCat0 [email protected]
issue-unpin will auto trigger when issues close

Signed-off-by: BetaCat0 [email protected]
@stale stale bot removed the issue/stale label May 25, 2019
@techknowlogick techknowlogick modified the milestones: 1.9.0, 1.10.0 Jun 4, 2019
@stale
Copy link

stale bot commented Aug 4, 2019

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 4, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Aug 4, 2019
@stale stale bot removed the issue/stale label Aug 4, 2019
@techknowlogick techknowlogick modified the milestones: 1.10.0, 1.11.0 Sep 3, 2019
@lunny
Copy link
Member

lunny commented Nov 16, 2019

Please resolve the conflicts.

@lunny lunny modified the milestones: 1.11.0, 1.12.0 Dec 13, 2019
@vtolstov
Copy link

any chance to get this upstreamed/merged? @BetaCat0 @lafriks @lunny
or we have issue with more generic solution?

@lafriks
Copy link
Member

lafriks commented Mar 20, 2020

I'm already working on label based priority implementation

@lunny lunny modified the milestones: 1.12.0, 1.13.0 May 2, 2020
@codecov-commenter
Copy link

Codecov Report

Merging #4823 into master will decrease coverage by 0.51%.
The diff coverage is 22.05%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4823      +/-   ##
==========================================
- Coverage   37.87%   37.35%   -0.52%     
==========================================
  Files         328      308      -20     
  Lines       48255    45567    -2688     
==========================================
- Hits        18276    17022    -1254     
+ Misses      27350    26079    -1271     
+ Partials     2629     2466     -163     
Impacted Files Coverage Δ
models/error.go 32.48% <0.00%> (-0.94%) ⬇️
modules/auth/repo_form.go 39.00% <ø> (ø)
routers/api/v1/repo/issue.go 22.72% <0.00%> (-7.31%) ⬇️
models/transaction.go 40.00% <40.00%> (ø)
routers/repo/issue.go 32.33% <40.74%> (-4.25%) ⬇️
models/issuse_priority.go 50.00% <50.00%> (ø)
models/issue.go 48.68% <80.00%> (+1.09%) ⬆️
routers/api/v1/api.go 75.48% <100.00%> (+1.71%) ⬆️
routers/routes/routes.go 86.26% <100.00%> (+1.20%) ⬆️
routers/api/v1/user/key.go 8.33% <0.00%> (-43.65%) ⬇️
... and 148 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b36402...300b19e. Read the comment docs.

@lunny lunny modified the milestones: 1.13.0, 1.14.0 Sep 1, 2020
@6543 6543 modified the milestones: 1.14.0, 1.15.0 Jan 18, 2021
@techknowlogick techknowlogick modified the milestones: 1.15.0, 1.16.0 Jun 15, 2021
@techknowlogick techknowlogick removed this from the 1.16.0 milestone Sep 9, 2021
@AlexWayfer
Copy link

@techknowlogick closed this 4 minutes ago

Why?

@6543
Copy link
Member

6543 commented Sep 9, 2021

because: very stale; a better generic solution was proposed, ...

@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
@delvh delvh removed the type/changelog Adds the changelog for a new Gitea version label Oct 7, 2023
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. type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

Successfully merging this pull request may close these issues.