<< Back to previous view

[QB-3253] "Create GitLab issue" step fails if no milestone defined
Created: 14/Sep/18  Updated: 18/Sep/18

Status: Resolved
Project: QuickBuild
Component/s: None
Affects Version/s: 8.0.14
Fix Version/s: 8.0.20

Type: Bug Priority: Major
Reporter: Alexey Shumkin Assigned To: Unassigned
Resolution: Fixed Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown
Environment: Operating System Linux 4.4.0-134-generic, amd64
JVM OpenJDK 64-Bit Server VM 1.7.0_111, Oracle Corporation
QuickBuild Version 8.0.14 - Mon Jul 30 09:20:03 UTC 2018


 Description   
"Create GitLab issue" step fails if no milestone defined.

My workflow supposes just to create an task/issue for a tester to test a some nightly build. But I cannot do that because Milestone seems to be a mandatory field and a step fails with the error:
23:38:53,863 ERROR - Step 'master>create-gitlab-issue' is failed.
    com.pmease.quickbuild.plugin.tracker.core.TrackerException: Unable to find milestone with name null
        at com.pmease.quickbuild.plugin.scm.gitlab.GitLabClient.getMilestone(GitLabClient.java:167)
        at com.pmease.quickbuild.plugin.scm.gitlab.GitLabClient.createIssue(GitLabClient.java:173)
        at com.pmease.quickbuild.plugin.scm.gitlab.issue.CreateIssueStep.createIssue(CreateIssueStep.java:36)
        at com.pmease.quickbuild.plugin.scm.gitlab.issue.CreateIssueStep.run(CreateIssueStep.java:28)
...

Steps to reproduce:
1. Setup the GitLab issue tracker in a configuration settings
2. Add a "Create GitLab Issue" step to a workflow. Fill the necessary fields. Do not specify anything in the "Milestone" field.
3. Run a build.
4. Step of the issue creation fails with the error above

I guess an issue must be created if no milestone specified. And must fail if the milestone value is defined but not found.

 Comments   
Comment by Alexey Shumkin [ 14/Sep/18 09:47 PM ]
the same issue for "Assignee"
Comment by Alexey Shumkin [ 18/Sep/18 08:27 PM ]
I confirm fix
Generated at Thu Apr 25 10:39:26 UTC 2024 using JIRA 189.