Cloud Jira Cloud Bitbucket: Jira ticket assingment to pipeline slow

[Stan van den Broek]

Hello fellow community members,

The setup we have implemented as follows:

We have Jira Cloud and Bitbucket Cloud. When we start a pipeline with deployment production a Jira Ticket is created and assigned to the pipeline and was also visible in Bitbucket pipeline. See screenshot below:

This all worked like a charm unit a few months ago but since then the assignement still works but the ticket isn't directly visible in the pipeline anymore. This takes more then 5 minutes. 

Lately the ticket numbers from old pipelines are gone but comeback over time. 

Is there a new setting that we are unaware of that sets a time limit on a trigger or something like that?

Could it be the amount of old pipelines? 

Does anybody have some indication where we could look for the solution?

Sorry about it to be a bit vague but it's a not really clear to us why it is happening. 

Thanks in advanced.

[Stan van den Broek]

We think we found the cause. 

The assignment of the ticket reassigns all the tickets to the all existing pipeline deployments. We have 11285+ pipelines so this takes awhile. 

In our understanding this standard functionality from Atlassian.

(Created a support ticket)