It gives 2 scenarios of the same name, here confusion occurs about which scenario to choose. One is the independent scenario, while the other is the copy of the independent scenario that was created when the independent scenario was imported into the masterclass. This creates confusion for the users to choose, which is the independent scenario to import.
In an independent scenario case, only the independent scenarios should be shown and all the copies of that scenario should be ignored, the copied version of that scenario should be shown in the masterclass or project section, from where we want the scenarios to be inserted in our new content.
My POV:
We can use the is_standalone attribute to filter the standalone scenarios, and only show that scenarios, in the independent scenarios list:
It gives 2 scenarios of the same name, here confusion occurs about which scenario to choose. One is the independent scenario, while the other is the copy of the independent scenario that was created when the independent scenario was imported into the masterclass. This creates confusion for the users to choose, which is the independent scenario to import.![image](https://github.com/enqurious/enqurious-platforms-bug-reporting/assets/105622461/4d5a90c8-f78a-48ac-acce-230380035bee)
In an independent scenario case, only the independent scenarios should be shown and all the copies of that scenario should be ignored, the copied version of that scenario should be shown in the masterclass or project section, from where we want the scenarios to be inserted in our new content.
My POV: We can use the![image](https://github.com/enqurious/enqurious-platforms-bug-reporting/assets/105622461/583018d5-6ee6-4dd5-8f07-483231f71fc9)
is_standalone
attribute to filter the standalone scenarios, and only show that scenarios, in the independent scenarios list: