Issue Summary

Jira Version Warnings do not report "Unreviewed Code" added after pull request was merged using Bitbucket (with automated transitions setup)

We need the JIRA provided data concerning these warnings to be accurate.

Steps to Reproduce

Steps:
1) create feature/ branch from JIRA (issue goes to In Progress)
2) create commits on that feature/ branch with the the JIRA issue key in commit message
3) create and complete a pull request for that feature/ branch (issue goes to In Review then completed). Pull request has been merged now. 
4) create additional new commit on that feature/ branch & push to the server. 
5) review JIRA detailed releases view for the assigned fix version 

• No warnings for the additional unreviewed commit which was after the merge.

• The issue is listed in the issues done" section.
• The extra commit is listed in the commits from the development column commit link 
• The bitbucket pull request does not list the commit not reviewed for the issue. 

Expected Results

1. For Jira to report in the warning section about the "unreviewed Code" for the issues which have merged pull request, and additional commits (un-reviewed)  has been added to an issue.

Or

2. Jira and/or Bitbucket should be configured to prevent post PR merge commits from being made to assure that the JIRA unreviewed code report is always accurate.

As KB for Merge a pull request states, Merging your changes is the final stage of the pull request process, hence Bitbucket should not allow further commits to be added, as per my knowledge, Github won't allow this. 

Actual Results

Jira does not warn about the "unreviewed Code" for the issues which have merged pull request, and additional commits (un-reviewed)  has been added to the issue. The report is inaccurate.

Workaround

No workaround exists. The report is inaccurate and not usable. 

Asking developers not to make commits after pull request is merged is not an acceptable workaround for customers.