gitea
gitea copied to clipboard
go-gitea
add filter by author/assignee in /issues #25979
https://github.com/go-gitea/gitea/assets/50507092/00abebdb-5ad3-4775-87d5-b71f4f84dbed
~~I pulled it down and tested it, and as if this PR wasn't already done?~~
~~The contents of the dropdown box are also empty~~
I apologize for pulling the wrong branch.
@lunny Since #26657 has been resolved by now. Is there anything else preventing this PR from being progressed or resolved? We would also love to see this being integrated into Gitea.
Whats the status here? if we update branch for conflicts - will you merge? its a very simple improvement :( Also - we plan to add label and milestone filters to this page too (we need them) - and jira-like drag'n'drop planning.. But we need a way to get our PRs merged :( @lunny WDYT ? the planning would just be a 'checkbox' - that would show 4 weeks ahead segments - simply looking at due date - and show a box on left side for each of the 'next 4 weeks' - making it super simple to find your issue and drag it to the left onto the week you want it to be 'done' and UI will set the due date for the issue to end of that week - and updating will then show the issue in the week it was set for.. (and then properly add selector for issues per page - so we can show entire 4 weeks of plans if we want it on one page or something).
This would help us use gitea for proper planning.. simply select a milestone (btw. we have added global milestones (will push PR very soon) - helps us group issues across repos based on features we work on) - and then we can just drag'n'drop to a week - and use our team labels - to easily see the plan for coming 4 weeks per team - and to fill those 4 weeks from our milestones.
We were discussing putting 'planning' in a diff. page than issues - but its actually very few addons needed for it to work properly - so seemed very much like duplication.. Unless we write it so it uses the API to fetch tickets - ie. less static.. speakup if you prefer we do it that way.. we really want our improvements merged - so they benefit all.. we are afterall a company that prefers to ONLY do open source development - and its sad to see it never getting merged :cry:
Whats the status here? if we update branch for conflicts - will you merge? its a very simple improvement :( Also - we plan to add label and milestone filters to this page too (we need them) - and jira-like drag'n'drop planning.. But we need a way to get our PRs merged :( @lunny WDYT ? the planning would just be a 'checkbox' - that would show 4 weeks ahead segments - simply looking at due date - and show a box on left side for each of the 'next 4 weeks' - making it super simple to find your issue and drag it to the left onto the week you want it to be 'done' and UI will set the due date for the issue to end of that week - and updating will then show the issue in the week it was set for.. (and then properly add selector for issues per page - so we can show entire 4 weeks of plans if we want it on one page or something).
This would help us use gitea for proper planning.. simply select a milestone (btw. we have added global milestones (will push PR very soon) - helps us group issues across repos based on features we work on) - and then we can just drag'n'drop to a week - and use our team labels - to easily see the plan for coming 4 weeks per team - and to fill those 4 weeks from our milestones.
We were discussing putting 'planning' in a diff. page than issues - but its actually very few addons needed for it to work properly - so seemed very much like duplication.. Unless we write it so it uses the API to fetch tickets - ie. less static.. speakup if you prefer we do it that way.. we really want our improvements merged - so they benefit all.. we are afterall a company that prefers to ONLY do open source development - and its sad to see it never getting merged 😢
Thank you for your patience, sorry there are too many issues/PRs that need to be handled. I think we can pick up this again.
having a milestone assigned do at least shine a light when a featurefreeze happens ... so I'll assign it now
about add filters etc ... to the global issue/pull dashboard, if not done right it gets more and more overloaded.
the a related current discussion happend at https://github.com/go-gitea/gitea/pull/29701#issuecomment-2004981973 for example ...
@6543 You are absolutely correct.. also the issue pages for repo vs. global are different - thats also very odd (and causes confusion). Primarily though its a huge problem, that you cannot filter issues on labels, milestones either - as that removes their usefulness (You can filter on labels if you can find an issue with the label and click on that.. LOL).
We have a couple of dedicated UX'es who, work on these problems every day - overload vs. functionality etc. - I'd gladly ask to give an opinion if you want. IMHO you need to first agree what features is needed - and then get someone with knowledge about people and such (UX) to design the page for how to implement the features, so they do not cause such overloads, but become natural.
I hope we do not disagree about the clear need for the ability to filter as such. Jira f.ex. has this - and its still a very popular product - so clearly that should not be in discussion :)