You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're currently managing around 200 issues on a gitea repository and it's getting increasingly difficult to manage which issues are more important than others. We're currently using labels like Priority: High to give us some level of granularity, but it would be easier if we could sort them manually to have a priorized backlog.
If #11161 get's merged, we could do it in a project with only one column if the issues are shown one above the other.
Or maybe currently there is a way to do it that I'm unaware of.
Thanks
The text was updated successfully, but these errors were encountered:
Hi, we're currently managing around 200 issues on a gitea repository and it's getting increasingly difficult to manage which issues are more important than others. We're currently using labels like
Priority: High
to give us some level of granularity, but it would be easier if we could sort them manually to have a priorized backlog.If #11161 get's merged, we could do it in a project with only one column if the issues are shown one above the other.
Or maybe currently there is a way to do it that I'm unaware of.
Thanks
The text was updated successfully, but these errors were encountered: