-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2021-11-04] Allow inviting multiple users to a workspace by reusing the OptionsSelector component #4775
Comments
Triggered auto assignment to @michelle-thompson ( |
Just commenting here to follow this discussion! |
I can work on this if you decide how the user interface should look. I have experience with |
Big fan of being consistent and using the same invite design as "New Group" for workspace invites. One small note is that you can invite multiple people in the current design by separating the emails by a comma so the "workaround" and "actual result" sections are a little off. I still think we should 100% make this change |
this seems like a good external candidate. Please share any proposals here and we'll get you hired for the Upwork job cc @kakajann @Santhosh-Sellavel |
Triggered auto assignment to @Julesssss ( |
Initial ProposalWe could reuse the code from IOUParticipantsSplit.js In WorkspaceInvitePage which is currently. Need to modify few lines as per our need here. Let's pause here. @MitchExpensify
|
One clarification will I get a bonus for this since issue #4668 which I raised was closed. And we are proceeding with this one. And changes I suggest in there are already implemented now. Thanks! |
We need to await the design before accepting any proposals here. CC @michelle-thompson One problem I see is that our previous usages of the OptionsSelector Component extend to the full page. In this case, we might need to reduce the height to include the personal message field. Another problem is that the component will extend infinitely as the user selects users to invite, further hiding the personal message field.
Thanks for the clarifying questions. There is no workspace user limit. We'll need to hold on to answering the other questions until the design is finalized. |
@Santhosh-Sellavel I think you have a reasonable claim to that bonus, but I don't think this is the right issue to claim the bonus on. Your initial proposal was to include a hint in the input field and as this was added as a part of this issue I think you should raise this point there instead. |
Before we get this on Upwork, I think we should nail down the design first. Does anyone agree? |
Just a suggestion. 2 screens would be good to solve this issue. 1st screen:
2nd screen
|
I can grab this one quickly @michelle-thompson I think it would be better if we could still keep the message and the user selection all on one screen... that being said, not sure if this feels a bit awkward but here is what we would have: Ideally the textarea would grow/shrink depending on the message in it too to save some space. Thoughts? |
Hey @marcaaron - it looks like this issue is related to what was initially reported here by Santhosh. Can you confirm I have this correct, this issue relates to fixing what was originally reported by Santhosh? If that's the case, then we'll want to pay Santhosh for originally reporting this issue (I will start that process). Thanks! |
Yeah, cool. Jules and I chatted about this briefly and here's where I think we've landed:
|
Ugh that privacy link... maybe it can go under the button so it's the bottom-most thing on the page? I'm not quite sure what else to do with it... |
Is it decided to place the Privacy link below the button? If so, Will it be left-aligned? cc: @shawnborton . And, please do look at the PR #5726 and let me know if you feel some improvements are needed. |
@parasharrajat would you mind placing the privacy link left-aligned under the button and sharing a screenshot? |
Will be done ASAP. |
@shawnborton, would you mind reviewing the screenshot from the PR here which shows the privacy link, thanks! |
Also, Can some send me the offer for this job? The job was closed a few days back. |
|
Reposted the job |
@mallenexpensify Done. |
Well. there is an issue with my PR. It is not excluding all the emails.
There are multiple sets here. Which one do I need to exclude? @marcaaron |
😦 hmm I am not too sure. But I think mainly you should not be able to invite the
What do you mean by this? Which emails are not being excluded? |
CONCIERGE , it was not part of EXCLUDED_GROUP_EMAILS. Ok, I will send follow-up. |
Ok I'm also not sure what |
Hired @parasharrajat in Upwork |
thanks for grabbing while I was at SuiteWorld @mallenexpensify! I can pick this up again from here |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.10-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2021-11-04. 🎊 |
Since this PR is in prod for 7 days and we can pay now - I paid Santosh for his proposal of this issue per this GH #4668 |
Paid @parasharrajat in Upwork, closed the job, closing this now too! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Expected Result:
When accessing the "Invite People" page we should be able to choose users from a list of our contacts (
personalDetails
) similar to how the Bill Split page works maybe?I'm not totally sure how we want this design to work yet and could use some feedback from design.
cc @JmillsExpensify @MitchExpensify
Actual Result:
We can only add one user at a time.
Workaround:
Can invite multiple people in the current design by separating the emails by a comma. This feature is not very clear as documented by @Santhosh-Sellavel in #4668
Platform:
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: