| << Back to previous view |
|
[QB-3257] Milestone is unset when GitLab issue is closed
|
|
| 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 |
|
Milestone is unset when GitLab issue is closed.
Steps: 1. Setup a GitLab issue tracker settings. 2. Add the "Update GitLab Issue" step to a workflow 3. Choose "Update issues with specified keys" for the "Specify How to Update Issues" setting. 4. Set "Issue keys" field value to an ID of an issue with a milestone set (it may be created earlier with the "Create GitLab Issue" step (nowadays it REQUIRES a milestone set)) 5. Set extra attributes to "action=CLOSE". 6. Run a build. The issue will be closed and its milestone will be unset. The milestone must not be unset. |
| Comments |
| Comment by Alexey Shumkin [ 18/Sep/18 08:26 PM ] |
| I confirm fix |