Issue Summary

When configuring Data Pipelines, we currently have the option to exclude commits from personal forked repositories using the property plugin.data.pipeline.bitbucket.export.personal.forked.repository.commits.

However, it would be beneficial to be able to exclude entire personal projects and/or repositories, including forked repositories, not just the commits. Ideally, these options should be available via the UI, in addition to the API/Bitbucket properties.

Another suggestion is to include the option to disable individual repositories instead of disabling entire projects, as some repositories might still be active and shouldn't be affected.

In summary:

• Add an option to remove personal projects from Data Pipeline exports.
• Add an option to remove specific personal repositories (rather than entire projects) from Data Pipeline exports.
• Provide UI options to make these adjustments.

These enhancements would help exclude unnecessary personal projects/repositories from the data export and prevent issues stemming from personal spaces, such as forked repositories pointing to nonexistent repositories, which can disrupt the entire data pipeline execution.

Steps to Reproduce

1. Configure the Data Pipeline export.
2. Observe that it exports all details, including those from personal spaces.

Expected Results

The data export can be configured with more granularity.

Actual Results

All details from personal spaces are exported.

Workaround

Remove entire personal spaces (including all repositories from those personal spaces) using the endpoint POST <base-url>/rest/datapipeline/1.0/config/optout.