if we have some milestones in the distant future and assign tickets to this milestone, because you do not want to decide now: at some day we will have plenty of these tickets to review again. Proposal is to have a backlog milestone for tickets that are
a) useful
b) not high prio
c) unclear situation who is going to work on it
in the milestone section instead of assigning this to an actual milestone.
List view
0 issues of 92 selected
- Status: Open.#813 In fossology/fossology;
- Status: Open.#1410 In fossology/fossology;
- Status: Open.#1395 In fossology/fossology;
- Status: Open.#1279 In fossology/fossology;
- Status: Open.#1315 In fossology/fossology;
- Status: Open.#1299 In fossology/fossology;
- Status: Open.#1318 In fossology/fossology;
- Status: Open.#1309 In fossology/fossology;
- Status: Open.#1292 In fossology/fossology;
- Status: Open.#1281 In fossology/fossology;
- Status: Open.#1271 In fossology/fossology;
- Status: Open.#1245 In fossology/fossology;
- Status: Open.#1243 In fossology/fossology;
- Status: Open.#458 In fossology/fossology;
- Status: Open.#249 In fossology/fossology;
- Status: Open.#289 In fossology/fossology;
- Status: Open.#1095 In fossology/fossology;
- Status: Open.#1212 In fossology/fossology;
- Status: Open.#1217 In fossology/fossology;
- Status: Open.#1222 In fossology/fossology;
- Status: Open.#1158 In fossology/fossology;
- Status: Open.#1147 In fossology/fossology;
- Status: Open.#1115 In fossology/fossology;
- Status: Open.#1091 In fossology/fossology;
- Status: Open.#1088 In fossology/fossology;