-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 1.0.4
-
Component/s: FishEye & Crucible integration
-
None
Just deployed 1.0.4, which has quite a few Perforce-related fixes (many thanks for these!)
Spotted a problem when you follow the "full change details" link, ie to .../commit on a Perforce project, which is where you get "Expression file.revision is undefined on line 370, column 127 in lib/components.ftl". I've attached the trace from the page to this issue.
Is there any chance that the change made for BAM-1096 has broken the functionality fixed in BAM-823?
Many thanks,
David
- was cloned as
-
BAM-1138 File Version Number problems with Perforce
-
- Closed
-