Klavs Klavsen

Great. I'll ask @VicOsewe to submit a PR, removing the limitation (so docs can stay the same :) - she's also an employee of Obmondo.com

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...

@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...

We use the "global milestones" overview - to have a central planning meeting across projects.. and many things actually requires changes across multiple repos - and for all those, we...

We would really like some feedback if you agree on the implementation plan - before we write the PR.. Our other 4 PRs seem to be stagnating (search for Obmondo.com)...

@denyskon if you could open up more about the process.. and if that process made it clear how we could help in making it easier for you to merge (and...

@lunny do you mean to suggest we add "org level milestones" - under projects? or just like projects is added? (ie. under org level menu) - as sep. menu bullit...

So use projects as milestones.. meaning we can't have issues from different milestones on same kanban? That would really suck for our workflow atleast :) (we have a kanban/project per...

and within 1 milestone - typicly there is tasks for different teams - so having 1 milestone tied to 1 project would also be bad :( (and also very weird...

Our suggestion would allow "org level" milestones to be chosen (or repo specific milestones) in same milestone selector on issue yes. Same way it works for labels. (where there is...