"Project Defaults": Groups Display & Management

[acshields]

Update A

Display the project's group question as follows on the "Project Defaults" screen:

• Field Label: "Intended Work Groups"
• Field Data: [Responsive Text Field]

Update B

When the user types into the responsive text field, the returned options should only be the groups that they have access too.

[vikasrohit]

@acshields we don't get Salesforce BA id when we lookup from our platform's BA API. So, we would need changes in SFDC to lookup for the BA in SFDC based on provided platform BA id.

[acshields]

@vikasrohit - was this comment supposed to be in regards to the issue(s) for billing account, and not for groups? If it was for groups, I am not understanding how a BA plays a role for that.

[vikasrohit]

@acshields sorry for the confusion, yes your are right my comment was in context of billing account #4269. I would comment in that issue for my intended concern.

However, I guess Update 2 is not necessary in this issue as well because groups does not have link to BAs as well.

[acshields]

@vikasrohit - updated to remove original "Update 2." Now reqs are labeled Update A and B and they should be accurate.

[maxceem]

@vikasrohit at the moment Project object doesn't have a designated place to store assigned groups.

We have 2 ways to go:

1. Create a new field groups in the project model to store the list of Groupd ids as array of string. See how we store terms "Project Defaults": Terms Display & Management #4273 (comment).
2. Store groups in the details field which is JSON and we can add any fields there.

I guess groups are kind of fundamental thing of projects and would hardly be dropped, so creating a separate field might have sense.

[vikasrohit]

Yes, agreed. we should make it first class citizen of the Project object because we might need to query projects based on groups.

[maxceem]

@vikasrohit I guess I found where we previously stored groups challengeEligibility.groups https://github.com/topcoder-platform/tc-project-service/blob/develop/src/events/projects/index.js#L114.

Though this field also only accepted numbers.

Should we update the type of it and reuse it? Or add a new one, what do you think?

[vikasrohit]

challengeEligibility is also one of the tech debt field which we are not using for any project. Even if it was set for some of the project initially, we are not reading it anywhere. So, we should be safe to introduce new field or reuse the same. However, I think having a dedicated field for groups make more sense to me. We could also think about create a new table called project_defaults OR challenge_eligibility, however, given the current requirements, I don't see any benefit of that. So, to avoid over engineering, I would suggest to go with a simple groups field which can accept array of UUIDs.