The SCM Changes list is invalidated after the pretest plugin has merged a ready-branch to master. This makes the list for the job and the jira notification contain invalid commit hash links.

I guess this is bacause of the squash commit that is used, making the commit on master different than the on that triggered jenkins, in tandem with the deletion of the branch causing stash to not find the commit in the repository. This makes the information presented misleading for users.

I would probably propose to either "change" the changes links provided by the git scm plugin to the new, squashed commit, keeping the old list in a separate pane if possible.

See attached images for how it looks in our jenkins/jira/stash setup.