Exclusion from build triggering causes exclusion from build results Revisions and Issues tabs

Summary

When exclusions are defined for a repository, revisions that contain only changes to excluded material do not trigger a build. These revisions also do not appear in the Revisions tab or the Issues tab even though all revisions since the last build are included in the build.

This behavior does not match the text in the UI : "Customise what files Bamboo uses to detect changes." (screenshot)

There is no documentation which covers this unexpected effect of excluding files/directories from build triggering.

Environment

• Bamboo 5.7.2
• Subversion

Steps to Reproduce

1. Create a build plan.
2. Create a global repository.
3. Under "Advanced" for the new repo enter a regular expression to exlude files from build triggering.
4. Create an excluded file and commit the change, referencing a JIRA issue in a comment.
5. Create an included file and commit the change.

The last commit will trigger the build but the prior commit and the issue it references will not appear in the build results.

Expected Results

• Revisions excluded from build triggering should appear in the Revisions tab because those changes are present in the build.
• Issues mentioned in revisions excluded from build triggering should appear in the Issues tab because those changes are present in the build.

Actual Results

• Revisions excluded from build triggering also do not appear in the Revisions and Issues tabs.

Example Use Case

A project where UI work is being done by one team and all the backend work done by another. The UI work will not use Integration testing and unit testing so the dev team does not want the UI work to trigger build/deployments (as this will trigger unit tests which are unnecessary). However, we do want to know what commits are in the build regardless of whether they were the trigger for the build or not. They are still significant changes just not the primary.

Workaround

No workaround has been identified.