
Key: |
QB-3257
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Alexey Shumkin
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 15/Sep/18 06:03 AM
Updated: 18/Sep/18 08:26 PM
|
|
Component/s: |
None
|
Affects Version/s: |
8.0.14
|
Fix Version/s: |
8.0.20
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
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
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
|
|
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.
|
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. |
Show » |
|