Milestone dropdown population causing issues when updating

[wolf99]

When a repository has no milestones the milestone dropdown in a Mylyn task is not being populated with none or whatever the GitLab equivalent is.
Thus Mylyn selects a blank milestone by default, which means that when updating any issue in such a repo from Mylyn (e.g. adding a comment to the task) it always adds a second comment for milestone removed which then also shows up in GitLab :(

[pweingardt]

Hi,
I can not reproduce this issue... could you give me more informations:

• Gitlab version (+ Ruby Version might be helpful)
• Plugin Version
• Eclipse Version

Thank you

[wolf99]

GitLab is 7.5.3 (Ruby: 2.1.4p265)
Mylyn plugin version: 3.14.2
Eclipse: 4.4.1 with CDT 8.5.0

Im not sure if I described the issue clearly first time around; basically, when I have no milestones in a project that has issues listed then the first time I update an issue via Mylyn it actually adds an extra item to the issue as viewed in GitLab, the extra item always being "milestone removed" even though there are no milestones and none were there to be removed in the first place.

I'm afraid I'm not a Java (or even desktop) dev otherwise I might know what more might be relevant, so if you need further info I'd be happy to provide it!

[wolf99]

I recently updated our GitLab CE install to 7.9.4 now and still see the issue.
I note in the GitLab issues pane, if I select None from the milestones drop-down, an issue that has been updated via MyLyn (and thus had the erroneous "Milestone removed" item added) does not show up. Seems to indicate that what MyLyn (or the connector) and GitLab use to indicate no-milestone-assigned does not match up.