| << Back to previous view |
|
[QB-2933] Update JIRA Issues may not work if perforce changelist description is over 250 chars
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 7.0.9 |
| Fix Version/s: | 7.0.11 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Benoit Maury-Bouet | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| 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 |
| Comments |
| Comment by Robin Shen [ 21/Mar/17 10:16 PM ] |
| Full change description can be retrieved as QB uses "p4 describe <change number>" to get the change description. So please check the issue update logic. |
| Comment by Steve Luo [ 22/Mar/17 03:14 AM ] |
|
A have tested with a very long commit message and don't find either or the problems. The message is not truncated, and issue command can process successfully.
Where do you see your commit message is truncated? Would you please show me your full commit message and the truncated message? If it is not suitable to attach some screenshots here, you can also send a mail to me (steve @ pmease). |
| Comment by Benoit Maury-Bouet [ 22/Mar/17 06:51 AM ] |
|
Thanks Steve i'm sending you an email
|