Sync Project between Connect App and Challenge Manager

[drasticdpk]

To Reproduce / Actual Behavior

• Login with copilot account on Connect App and Challenge Manger App.
• Here only Active project are listed on CM App. So copilot has to wait until project became Active status but they already got the access on the project at Connect App.

Expected behavior
Once copilot onboard on Connect App, he/she must have access to the respective project on Challenge Manager too.

Possible Solution

• Either we can fetch Project Status with Active, In Review [and/or Reviewed] too, so copilot can create the challenge.
• Or Connect App user must follow the process and make project Active state while onboarding the Copilot on connect app.
• We can add one more validation where system should allow to activate the challenge for only Active project.

Screenshots or Video

Note : I raised this issue based on my experience on connect app. Are we monitoring for connect user/Project, they are on correct process or not. I can see few project has already started but they are still in In-Review status.
cc @acshields @lakshmiathreya
Correct me If I was wrong and let me know for anything.

[acshields]

@vikasrohit @drasticdpk - My thought here on a future update: If a project is not in Active status and any user who has permissions to view Work Manager sets-up a challenge/task, then the project status would automatically update to Active at that time. So, in essence, lift the requirement for the project to be "Active" to complete a challenge/task set-up, and instead we can use a challenge/task set-up as a mechanism to update the project status to "Active" automatically.

[vikasrohit]

Either we can fetch Project Status with Active, In Review [and/or Reviewed] too, so copilot can create the challenge.
Or Connect App user must follow the process and make project Active state while onboarding the Copilot on connect app.
We can add one more validation where system should allow to activate the challenge for only Active project.

I agree with @drasticdpk for all 3 points. In fact we need all 3 to be implemented.

@acshields personally I don't prefer the automatic things happening behind the scene as that creates too much confusion among different users. I would still like to have strict process around managing projects which lacking. Managers use Projects app at their will and just for some data entry. No one is following the features as they are intended.

we can use a challenge/task set-up as a mechanism to update the project status to "Active" automatically.

Having challenge setup as a trigger to update project to Active automatically have another problem (apart from confusion who did what and when as I said above) and the problem is that one has to move project to Active status even when one is just trying to keep drafts of challenges. Having project in Active status might have its implications on the other processes e.g. Salesforce and can trigger many customer facing notifications (in future).
One important point is that project management is responsibility of Projects app and if we automatically make the project active from WM, it violets that responsibility.

[vikasrohit]

@acshields bumping it up for discussions