Note: for some inputs on the common issues, please refer to this article.

The code of the project is split between a common code-base and specific code in the Dataiku recipes, as highlighted in the project architecture.

The actions to take are different depending where the issue is located.

Option 1: Issue related to the code base (no change on the Dataiku project itself)

Create a fix branch from the code base repository dev branch.
If you need it to test your development, create a branch from the Dataiku project in design following these guidelines and switch the library to your new code base fix branch.
Make sure the fix does not break anything related to other GBU projects (you can create a branch based on your new code base in the CS or SPP project and run a "Full reload" scenario to make sure it is still working).
Make sure the Gitlab pipeline with the unit tests passes successfully.
Merge your fix branch for the code-base on dev (you can still refer to this page).
Update the Dataiku dev project library for the right GBU by selecting the "Reset from remote HEAD" option.
Launch a "Full reload" scenario on dev to make sure it runs properly
Merge your fix branch for the code-base on master (you can still refer to this page).
Update the Dataiku master project library for the right GBU by selecting the "Reset from remote HEAD" option.
Create a new bundle of the project and deploy it in automation.

Option 2: Issue related to the Dataiku project Flow (no change on the code base)