| Key: |
QB-2933
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Benoit Maury-Bouet
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Mar/17 04:04 PM
Updated: 28/Mar/17 11:46 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
7.0.9
|
| Fix Version/s: |
7.0.11
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
We realized some Jira issues were not progressed through QB.
I think the issue comes from Qb running "p4 changes" without "-l" or "-L" options
Our changes get truncated before QB can find the pattern for progressing jira issues or the correct issue to progress
I've flagged this as critical as our team is really using the feature
Thanks
|
|
Description
|
We realized some Jira issues were not progressed through QB.
I think the issue comes from Qb running "p4 changes" without "-l" or "-L" options
Our changes get truncated before QB can find the pattern for progressing jira issues or the correct issue to progress
I've flagged this as critical as our team is really using the feature
Thanks |
Show » |
| No work has yet been logged on this issue.
|
|
Update JIRA Issues may not work if perforce changelist description is over 250 chars