[SHEP-2] UI Created to Split a Single Campaign into Multiple Campaigns

[akhan-mozilla]

References

SHEP-2

Problem Statement

With the automatic creation of a child campaign when new booster deals are imported, we need a UI that allows to split a single campaign into multiple campaigns.

Proposed Changes

Split Campaign Form Added to Allow Users to Split a Single Campaign into Multiple Campaigns.

Verification Steps

1. Click on the "Split Campaign" icon on the Campaigns list page.
2. Click on the plus icon to split the campaign into multiple campaigns.
3. Add details for the newly created campaign.
4. Ensure the total net spend for the campaigns matches the actual value of the campaign before the split.

Visuals

Split_Campaign_feature.mov

[kauana]

Hey @akhan-mozilla how to run the app locally? I've run docker compose up --build inside dashboard and then access it at 0.0.0.0:5173. I'm getting this error:

Have you seen this before?

[cyptm]

Do we plan on defining return types for some of these functions?

[akhan-mozilla]

Since we already have types defined for all the mutate return functions used in there, we don't have to define the type here.

[cyptm]

Makes sense!

[cyptm]

Can we define the type for data?

[akhan-mozilla]

I noticed that the data returned in onSuccess here isn't being used, so I removed it. I'll check for any other missing return types and add them.

[akhan-mozilla]

Hey @akhan-mozilla how to run the app locally? I've run docker compose up --build inside dashboard and then access it at 0.0.0.0:5173. I'm getting this error:

Have you seen this before?

It seems the boostrProducts table is empty for you. However, I've updated the dashboard page to prevent errors when no product data is available.

[kauana]

Ok new error when I click on Campaign and "Add Data"

(Note that I've run the boostr script to populate the boostr product table)

[akhan-mozilla]

Ok new error when I click on Campaign and "Add Data"

(Note that I've run the boostr script to populate the boostr product table)

This doesn't seem to be related to the Boostr products since you are creating the campaigns. I just added a quick update; could you please try creating the new campaign again?

[kauana]

Can we please add the Jira story to the PR title so once we squash and merge it we can keep track of it?

[mashalifshin]

@akhan-mozilla Just popping in to make a quick reminder to manually run make eslint on these changes, since the CI checks don't do that for you yet.

(Just to be clear, not saying you should address any lint issues that aren't related to this PR, there are some on main already as you captured in SHEP-91(https://mozilla-hub.atlassian.net/browse/SHEP-91, but just wanted to make the reminder because it's so hard to remember when it doesn't happen automatically)