Assignee on Task doesn't persist

[ajefts]

Describe the bug
For some users (seems like a lot) there is an issue that happens when you assign the user to a task. NOTE: This also happens in Direct and I believe the root cause has something to do with some profile data (f2f rating) that legacy tries to lookup when assigning the user.

To Reproduce / Actual Behavior
Steps to reproduce the behavior:

1. Start creating a new task
2. Assign 'winterflame' (I know his user breaks)
3. Save the task as a draft (or any action that will sync to legacy)
4. Note that there is no error on the page
5. Refresh so you pull the latest data for the task. Note that the assignee is gone (might need to wait for sync to see this happen??)
6. Go to the challenge in Direct/OR and notice the assignee has not been set.
7. Now, from Direct edit the challenge and try to set the assignee. When you save, you will see the error. Check the Direct log at the same time for the specific error.

Expected behavior
Assignee should be saved on task or a useful error/validation message should be presented.

[ajefts]

fyi @acshields @vikasrohit

[acshields]

@vikasrohit - what req's do you need clarified?

[vikasrohit]

@acshields it is backend issue, and I have tagged the issue with API/Backend Question which means we need @rootelement's expert advice or help.

[maxceem]

@vikasrohit done via #936

As was discussed on Slack. Instead of getting the submitter role by name, we use role UUID defined in config. Because at the moment DEV data has multiple role with Submitter name, so we cannot rely on that at the moment.

IMO. If the ResourceRole.name suppose to be the source truth, maybe we can make name field unique in the ResourceRole model?

[vikasrohit]

@maxceem I think this issue is happening for only particular user. I thought it was happening because of the same reason we saw in dev but this issue is already happening on prod where the roles data is correct. But none the less we got it fixed in dev.

[lakshmiathreya]

@drasticdpk Assignee is persisting in my test. Pls re-verify in Prod and update the Test report.

[vikasrohit]

@lakshmiathreya the main issue here is assign task is not working for some of the users and one of the example is shared in the original description by Tony. We haven't fixed that yet.