jbauer opened 2 years ago
|
|||||||
In OneDev an issue can be associated with multiple milestones, and the backlog by default only shows issues not associated with current milestone, instead of any milestone. This is because:
So backlog issue is something very specific to site, and OneDev only puts minimum constraint on them (only filters those not belong to current milestone) . If you do not care about above points, you may simply edit your board to specify backlog base query as
|
|||||||
Back log description needs to be updated to reflect this though |
|||||||
Robin Shen changed fields 2 years ago
|
|||||||
I could swear I had done this last week and got an empty result, thinking that onedev produced a query like Then, as you said, UI help text should be updated to reflect the current behavior. Maybe also making clear that you can override the UI selection by added |
|||||||
Robin Shen changed state to 'Closed' 2 years ago
|
|||||||
If an issue is in backlog, OneDev will Closing it now, reopen if you observe odd things. |
|||||||
@robin you really thought of almost anything didn't you! Love this! :) |
|||||||
@jorydekort thanks for the kind words, and all the good suggestions. 😃 |
Type |
Question
|
Priority |
Normal
|
Assignee |
When creating two milestones A and B and then assign issues to A the backlog of milestone B shows issues that have been assigned to milestone A. However in the board configuration the help text of backlog back query says "Backlog issues are issues without any milestone" and IMHO that makes perfectly sense because when planning milestones you do not want to see anything assigned to other milestones.