Obelix Posted April 25 Share Posted April 25 Currently we have 97 Issues without a Milestone listed on Gitea. The oldest one has been opened 4 years ago, but it seems to me that new Issues without a Milestone increased since the migration from Trac to Gitea. Shall all Issues without a Milestone be backlogged? If yes, I'd proceed. Quote Link to comment Share on other sites More sharing options...
Atrik Posted April 25 Share Posted April 25 Probably something to do per-case. Backlogging seems to be worse case to me. Maybe if the issue seems important we could add arbitrary milestones. Also I don't know if it's somewhat impolite but maybe assigning members that have skillset and bear interest in the area that the issue touches, could nudge some to pick up the issue. 1 Quote Link to comment Share on other sites More sharing options...
phosit Posted April 26 Share Posted April 26 I'd say "Must Have"s and "Release Blocker"s should have the next release as milestone. The others should be backlogged. 1 Quote Link to comment Share on other sites More sharing options...
hyperion Posted April 27 Share Posted April 27 Backlog milestone to my understanding is because on trac you couldn't have no milestone assigned. So no milestone and backlog are defacto the same. Personally I prefer no milestone to backlog, tho looks a bit awkward if there are only a few with no milestone. Anyway I treat them the same. Quote Link to comment Share on other sites More sharing options...
Stan` Posted Monday at 13:17 Share Posted Monday at 13:17 No milestone in Trac was for deleted tickets. Quote Link to comment Share on other sites More sharing options...
Obelix Posted 38 minutes ago Author Share Posted 38 minutes ago Thanks for your replies! On 27/04/2026 at 3:17 PM, Stan` said: No milestone in Trac was for deleted tickets. Every open Issue has a Milestone now, the ones formerly without one got backlogged. On 26/04/2026 at 12:34 PM, phosit said: I'd say "Must Have"s and "Release Blocker"s should have the next release as milestone. The others should be backlogged. In the next step, all Issues with Milestone "Backlog" and the priority label "1: Release Blocker" have been set to Milestone "Release 29". Right now, I have set all backlogged Issues that have the priority label "2: Must have" to Milestone "Release 29". For me, this case is now closed. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.