Steve is correct. The Array of Guids, which is the data type you would want to use, was only added to the module builder which is what Radoslav is referencing in the article. I know it isn't the best way, but you could go the opposite route. You could create the association from the Issues module and reference the news.
Again not the proper relationship approach, but it would achieve your purpose. Another thing you could do would be to create a new taxonomy and use it as the link between the two. You could add the new taxonomy to the news and also the Issues. Make sure you use the same taxon on both. Then when you display the news, you would create an external template and then use the API to get a list of the issues with the same taxon that was applied to the news item. If you specify the ID of the page that you have the control to display the Issues, then you could link to the detail of the issue. Then you could create another external template for your Issue detail and do the reverse. Filter out the news based on the taxon of the Issue and link it back.
This may not be the best solution, but it may help you continue on until a later release. The need for the external template is so you can add in some extra coding as the widget templates in Sitefinity do not allow you to add in extra code other than inline and this wouldn't work.
One other bit of help if you go this route. As I mentioned, if you know the id of the page that will host the details of each, you can use the following helper method to generate the url of the item:
Telerik.Sitefinity.Web.DataResolving.DataResolver.Resolve(DataItem, "URL", "", PageID)
In the databinding of the news or issues, depending on the template, you can call this helper method. The DataItem is the current item being bound, and then PageID is the ID of the page that the item should link to.
I hope this helps you out until the content linking comes out.