| Key: |
QB-1258
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Steve Luo
|
| Reporter: |
TODAY SYSTEMS
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Apr/12 12:44 AM
Updated: 26/May/12 12:21 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
4.0.40
|
| Fix Version/s: |
4.0.40
|
|
|
Original Estimate:
|
1 week
|
Remaining Estimate:
|
1 week
|
Time Spent:
|
Unknown
|
|
Environment:
|
Non SCM environment
|
|
|
We found that if we do not use any SCM like SVN or Git, QB doesn't link it's build ID to the Artifact which QB create automatically to TeamForge with "Create TeamForge Artifact step".
I think it's very important to link a build should link it's Tracker issue especially if a Tracker issue is created by a build automatically because people used to think that TeamForge is seamlessly linked to QuickBuild.
I know we can link a Tracker issue to QB manually, but everybody knows human always make errors or mistakes.
|
|
Description
|
We found that if we do not use any SCM like SVN or Git, QB doesn't link it's build ID to the Artifact which QB create automatically to TeamForge with "Create TeamForge Artifact step".
I think it's very important to link a build should link it's Tracker issue especially if a Tracker issue is created by a build automatically because people used to think that TeamForge is seamlessly linked to QuickBuild.
I know we can link a Tracker issue to QB manually, but everybody knows human always make errors or mistakes. |
Show » |
| There are no comments yet on this issue.
|
|
Automatically link to TeamForge Artifact which is created by QuickBuild with "Create TeamForge Artifact step"