Issue Summary

This is reproducible on Data Center: YES

Steps to Reproduce

1. In Bitbucket Cloud:
   1. Prepare workspace with TEST repository
   2. Create 12 branches and corresponding PRs. Name them according to pattern "PR-1", "PR-2" etc. Names just help us to sort them from the oldest to the newest.
   3. Go to "PR-5" and mark it as "Request changes"
2. In Jira:
   1. Link created Bitbucket cloud workspace with DVCS
   2. Wait till linking finished
   3. Run soft-sync in repositories list page for TEST repository

Expected Results

All 12 PRs will be stored in "AO_E8B6CC_PULL_REQUEST" database table.

Actual Results

1) Only couple (probably 5)  pull requests will be stored in "AO_E8B6CC_PULL_REQUEST" database table.

2) Log will contain line with pattern:

[c.a.j.p.d.s.b.c.m.repository.pullrequest.BitbucketPullRequestActivityEnvelopeDeserializer] Unknown type of activity :  {json_payload}

Workaround

Currently there is no known workaround for this behavior. Change is needed to be done in production code itself.