Key: |
QB-2633
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
max1234
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 03/Feb/16 03:10 AM
Updated: 11/Feb/16 05:29 AM
|
|
Component/s: |
None
|
Affects Version/s: |
6.1.3
|
Fix Version/s: |
6.1.5
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Hi Steve,
Just a small request, as validation step is in groovy, we are able to add logging which gives details on what operation is taking place etc.
With the JIRA update step and others as well, there is no logging at all. Can there be a bit more logging added just so that when we see history of some of these steps, we know what QB carried out in terms of JIRA updates or other tasks.
Also, if a field which does not exist is added to extra attributes , e.g. "comments" instead of "comment", there is no error and the step simply succeeds, making it very misleading. Thus the logging and also failures to update fields would be great to have and really help solidify the update step.
|
Description
|
Hi Steve,
Just a small request, as validation step is in groovy, we are able to add logging which gives details on what operation is taking place etc.
With the JIRA update step and others as well, there is no logging at all. Can there be a bit more logging added just so that when we see history of some of these steps, we know what QB carried out in terms of JIRA updates or other tasks.
Also, if a field which does not exist is added to extra attributes , e.g. "comments" instead of "comment", there is no error and the step simply succeeds, making it very misleading. Thus the logging and also failures to update fields would be great to have and really help solidify the update step.
|
Show » |
There are no comments yet on this issue.
|
|