How to resolve warnings without viewing the code

Question

We are using Jira 6.4.1 connected to the 4.3.2 bit bucket. When I watch releases for my project, I see a series of warnings for some specific Jiras. A warning:

Raw Code These issues have been flagged as completed, but commits are not part of the pull request or review.

Usually, as my workflow, I can click, makes a direct call to the repo without checking the code; but the problems listed seem a bit random, and I can train what has been done with them.

What causes this condition and warning, and how can I solve it?

Answer 1

This warning is caused by the fact that the jira command key is used in commits, but this key is not displayed in the transfer or view request. It is assumed that all code included in this version should be reviewed.

There are two ways to remove this warning. The first is to change the development process and start using pull requests instead of doing direct management.

The second is to disable this warning. The warning tab should have a Manage Alerts button, which opens a dialog in which you can choose what will trigger the warning. You want to clear the Unviewable code check box.

Answer 2

This problem can occur regardless of the use of retrieval requests, for example, if someone refers to the problem only in the merge commit message.

To fix this problem and get rid of the warning, you can create an empty commit ( git commit --allow-empty -m "Review ISSUE-13" ) in a new branch that refers to all the problems raised by the commit message. Then open a retrieval request for it and merge it as usual. Jira sees that the delete request has been merged and the warning has been reset.