Preventing duplicate data when usual normalization only makes sense for some of the records
You may want to normalize out the comments field to allow for a comments chain.  This may have additional fields such as userid and date.  This might result in a table tracking actions on issues.  If this is not part of your design, I wouldn't normalize the comments field out.  

It appears you have an optional 1-1 relationship between the status checks and issues.  Either table can carry this relationship as a nullable foreign key.  If the relationship might not be 1-1 that may drive the table carrying the foreign key, or require a relationship table.