Updated issue numbers to be links to github issues.

Author: jgebal

_posts/2018-03-29-cli-version3.1.0-released.md

@@ -30,12 +30,12 @@ We encourage you to always use the latest version of cli to communicate with a v
 
 *Enhancements*
 - Support for custom reporters. Just call utplsql run user/pass@connstr -f=my_custom_reporter and cli will try to use a database-reporter with the given name
-- Assets necessary for CoverageHTMLReporter are written to $outputFileName-assets folder (utPLSQL/utPLSQL-java-api#39)
-- Realtime-Feedback: Output to screen is immediate, output to files is in bulks (#68)
-- NLS-Support from environment (#56)
+- Assets necessary for CoverageHTMLReporter are written to $outputFileName-assets folder ([https://github.com/utPLSQL/utPLSQL-java-api/issues/39](utPLSQL/utPLSQL-java-api#39))
+- Realtime-Feedback: Output to screen is immediate, output to files is in bulks ([https://github.com/utPLSQL/utPLSQL-cli/issues/68](#68))
+- NLS-Support from environment ([https://github.com/utPLSQL/utPLSQL-cli/issues/56](#56))
 
 *Bugfixes*
-- The correct usage is now stated in help message (#63)
+- The correct usage is now stated in help message ([https://github.com/utPLSQL/utPLSQL-cli/issues/63](#63))
 - Several small improvements
 
 For more info on improvements and fixes, check out the [blog post from Samuel Nitsche](https://cleandatabase.wordpress.com/2018/03/29/open-source-engagement-for-utplsql/)

_posts/2018-07-20-version3.1.1-delayed_announcement.md

@@ -14,8 +14,8 @@ On April 25th, a major release 3.1.0 of utPLSQL was published on github and the
 Right after the release two issues were found resulting in bug fixes and release 3.1.1
 
 ## Version 3.1.1 bug-fixes
-- Block coverage reporting doesn't work on schema other than framework owner (#653)
-- Reporter threads timeout and do not produce outputs when running with `utplsql-cli` and idle time exceeds 1 minute (#652)
+- Block coverage reporting doesn't work on schema other than framework owner ([https://github.com/utPLSQL/utPLSQL/issues/653](#653))
+- Reporter threads timeout and do not produce outputs when running with `utplsql-cli` and idle time exceeds 1 minute ([https://github.com/utPLSQL/utPLSQL/issues/652](#652))
 
 [Release 3.1.1 download page](https://github.com/utPLSQL/utPLSQL/releases/tag/v3.1.1)
 
@@ -51,7 +51,7 @@ Right after the release two issues were found resulting in bug fixes and release
 * Added [`include()` and `exclude()` extensions](https://github.com/utPLSQL/utPLSQL/blob/develop/docs/userguide/advanced_data_comparison.md#excluding-elements-from-data-comparison) to cursor and object/collection data comparison
 * Added [`diff` functionality](https://github.com/utPLSQL/utPLSQL/blob/develop/docs/userguide/expectations.md#diff-functionality-for-compound-data-types) for cursor, object and collection data 
 * When comparing cursors, column data-type is now also checked for equality
-* Changed behavior of execution of `ut.expect()` on closed cursor (#548)
+* Changed behavior of execution of `ut.expect()` on closed cursor ([https://github.com/utPLSQL/utPLSQL/issues/548](#548))
 * Added support for cursors with implicitly named columns
 
 #### General improvements
@@ -64,14 +64,14 @@ Right after the release two issues were found resulting in bug fixes and release
 * Migrated part of old script-based tests to new utPLSQL v3 tests
 * Documentation fixes and improvements
 * Reporters now provide a method to get description
-* Test execution continues even when encountered `Existing state of packages was discarded/invalidated` exceptions (`ORA-04068`/`ORA-04061`). The whole suite will execute, test result reports will be available and the exception will be re-thrown to the user after the run was finished. (#504)
+* Test execution continues even when encountered `Existing state of packages was discarded/invalidated` exceptions (`ORA-04068`/`ORA-04061`). The whole suite will execute, test result reports will be available and the exception will be re-thrown to the user after the run was finished. ([https://github.com/utPLSQL/utPLSQL/issues/504](#504))
 
 ### Bug-fixes
-* Coverage schema had to be explicitly provided, even when using `a_include_objects` (#511)
-* utPLSQL fails to run, when one of suite packages has no newline between `--%suite` and procedure-specific annotations. (#514 / #516)
-* Fixed false-negative code coverage reporting on labelled `end loop ` elements (#539)
-* Fixed issue with invalid suite grouping when running `xunit_reporter` (#547)
-* Code coverage was always showing first report gathered in a session (#562)
-* Wrong format of time in XUnit_reporter when running on German locale (using comma as decimal separator) (#572)
-* Fixed issue with wrong exception getting thrown when suite failed and there was a pending distributed transaction (#601)
-* Fixed file-mapper issue where two files were mapped into the same object and caused `ORA-00001: unique constraint (UTP3.UT_COVERAGE_SOURCES_TMP_PK) violated` (#568)
+* Coverage schema had to be explicitly provided, even when using `a_include_objects` ([https://github.com/utPLSQL/utPLSQL/issues/511](#511))
+* utPLSQL fails to run, when one of suite packages has no newline between `--%suite` and procedure-specific annotations. ([https://github.com/utPLSQL/utPLSQL/issues/514](#514) / [https://github.com/utPLSQL/utPLSQL/issues/516](#516))
+* Fixed false-negative code coverage reporting on labelled `end loop ` elements ([https://github.com/utPLSQL/utPLSQL/issues/539](#539))
+* Fixed issue with invalid suite grouping when running `xunit_reporter` ([https://github.com/utPLSQL/utPLSQL/issues/547](#547))
+* Code coverage was always showing first report gathered in a session ([https://github.com/utPLSQL/utPLSQL/issues/562](#562))
+* Wrong format of time in XUnit_reporter when running on German locale (using comma as decimal separator) ([https://github.com/utPLSQL/utPLSQL/issues/572](#572))
+* Fixed issue with wrong exception getting thrown when suite failed and there was a pending distributed transaction ([https://github.com/utPLSQL/utPLSQL/issues/601](#601))
+* Fixed file-mapper issue where two files were mapped into the same object and caused `ORA-00001: unique constraint (UTP3.UT_COVERAGE_SOURCES_TMP_PK) violated` ([https://github.com/utPLSQL/utPLSQL/issues/568](#568))