History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2933
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Benoit Maury-Bouet
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Update JIRA Issues may not work if perforce changelist description is over 250 chars

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


 Description  « Hide
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

 All   Comments   Work Log   Change History      Sort Order:
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.

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).

Benoit Maury-Bouet [22/Mar/17 06:51 AM]
Thanks Steve i'm sending you an email