![\"Visual](\"https:\/\/www.almtoolbox.com\/images\/annotate-removed-lines-function.png\")
<\/a>Figure 1: Line #42 indicates that it was checked-in by \u2018yuval\u2019 on 11\/14\/2012 through version \\main\\BankDev_1.0\\Integration\\2<\/p><\/div>\n
This feature is\u00a0particularly\u00a0useful when you have dozens or hundreds of file versions\u00a0and you can\u2019t\u00a0readily\u00a0open the Version Tree\u00a0for each one\u00a0and quickly ascertain\u00a0into\u00a0exactly which one\u00a0of the many existing versions\u00a0your \u201dtarget\u201d code was checked-in.<\/p>\n
Using Visual Annotate<\/em>, you get the answer immediately; accurately and hassle-free! Figure 2: You can quickly see that line #12 was checked-in through activity named \u2018annotate-test\u2019<\/p><\/div>\n Furthermore, if your bug tracker is ClearQuest (UCM-enabled), you automatically see the record ID. Figure 3: In this example, we track the file backgroundtask.java (see the code lines in the middle). You can see the annotated data to the left (date i.e. when it was checked-in; by whom; on which version) and then compare differences .vs. file version 5 to the right far right column)<\/p><\/div> Figure 4: Using colors you can easily see that lines #112-113 and #129-130 were checked in via the same activity ‘E6008’ \u2013 so they may mutually affect one another<\/p><\/div>\n These are only 4 usages of the 33+ already reported by users. (More examples coming soon – Stay informed by registering for our newsletter<\/a>)<\/p>\n See a quick demo (3 min.) on YouTube: <\/strong>
\n
\n2. Using ClearCase UCM? Quickly find out via which activity your code lines came<\/strong><\/p>\n<\/a>
\n
\n3. Get the full picture: your code + annotated data + diff to another file version, so you can see them in one dashboard (!) for a better root cause analysis:<\/strong><\/p>\n<\/a>
\n
\n4. Quickly see correlations between code lines:<\/strong>
\nVisual Annotate<\/em> enables you to color the code lines by some criteria, including file versions, dates, users and UCM activities. This helps you to easily find out which lines have been put together.
\nUsing color layers to find out the context between code lines can help drill down and find the reason of a change or why a bug occurs.<\/p>\n<\/a>
\n