-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2023-05-16] [$2000] Workspace - When adding a new member, add another screen to invite users #15083
Comments
Triggered auto assignment to @mallenexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~0182c8f1bfbd7b65ae |
Current assignee @mallenexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr ( |
Triggered auto assignment to @thienlnam ( |
Guessing this can be external. I did a quick-check to see if this bug might be occurring in other places on the app but wasn't able to find. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The screen is covered by the the personal message view thus the user cannot see the input box where they are typing. What is the root cause of that problem?the root cause is using the What changes do you think we should make in order to solve the problem?We should remove the |
ProposalWhen the height of the screen is small and the height of the keyboard is large, the pop-up invitation message input box will cover the above search box We'd better move this invitation message input box to another new page App/src/pages/workspace/WorkspaceInvitePage.js Lines 263 to 274 in e31cb53
inviteUser() {
...
this.setState({shouldDisableButton: true}, () => {
const logins = _.map(this.state.selectedOptions, option => option.login);
const filteredLogins = _.uniq(_.compact(_.map(logins, login => login.toLowerCase().trim())));
- Policy.addMembersToWorkspace(filteredLogins, this.state.welcomeNote || this.getWelcomeNote(), this.props.route.params.policyID);
- Navigation.goBack();
+ Navigation.navigate(ROUTES.getWorkspaceInviteMessageRoute(this.props.route.params.policyID, filteredLogins))
});
} class WorkspaceInviteMessagePage extends React.Component {
render() {
return (
...
<TextInput
label={this.props.translate('workspace.invite.personalMessagePrompt')}
autoCompleteType="off"
autoCorrect={false}
numberOfLines={4}
textAlignVertical="top"
multiline
containerStyles={[styles.workspaceInviteWelcome]}
value={this.state.welcomeNote}
onChangeText={text => this.setState({welcomeNote: text})}
/>
...
);
}
} _1.mp4Waiting for your suggestions |
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
ProposalPlease re-state the problem that we are trying to solve in this issue.When keyboard is open on the new member invite page, the user list and search box is partially hidden. What is the root cause of that problem?We show invite button component, privacy message component, invite message component above the keyboard on user searching the user list. As keyboard takes considerable amount of screen space and other components mentioned above also takes considerable screens space, we are end up with only limited screen space to show the search and list component. What changes do you think we should make in order to solve the problem?There are multiple ways to solve this.
@mallenexpensify But regardless of any option, we would require answer from design team to let us know what is the expected behaviour and what components to show. I can make the required changes from the design team as well. Optional: What alternative solutions did you explore? (Optional)None |
@mollfpr can you please review the above proposals?
@abdulrahuman5196, correct, thanks for pointing out. I was able to reproduce but didn't think of how we should show. I wonder if we should just minimize this area, possibly removing some/most of the text? (sorry, I have a weird issue where Github doesn't allow me to post images) |
Reviewing proposals now! |
@priyeshshah11 I try your solution, but it's not working. @abdulrahuman5196 Could you provide the screenshot for your suggestion before we ask for the design team's opinion? |
Thanks @mollfpr, my bad I don't know why it worked for me then but it's not working now. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The screen is covered by the the personal message view thus the user cannot see the input box where they are typing. What is the root cause of that problem?the root cause is that the list height shrinks which is causing the personal message view to move up along with the keyboard & cover the search & list. What changes do you think we should make in order to solve the problem?We should give the view around the optionsSelector a min height to fix the message box overlapping issue (Tested it properly this time, haha) |
@priyeshshah11 Could you share the screenshot of the result? |
@mollfpr Screenshot for above proposal |
Sorry @priyeshshah11 on second thought will be helpful if you can record it with focus the search input and focus on the message input 😅 |
@mollfpr There you go RPReplay_Final1676461339.mov |
Possible merge conflict with PR, being worked on #15672 (comment) |
@mallenexpensify, @mollfpr, @thienlnam, @abdulrahuman5196 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Not overdue. PR is pushed and in staging. Waiting for prod deployment, assuming it should happen sooner, since it has been couple of days in staging. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.12-0 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 2023-05-16. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Hi team, I think it would be fair to re-evaluate the compensation for this feature request issue. Since we had to do more stretch to get this feature request into going. On high level, This involved refractor of MultipleAvatars component from hard coded values to generic implementation which made the component much scalable for future usecases, minor refractors on Form component as well, and the creation of new page itself and further polishes and followups which took month's effort to get the feature rolling. PR reference - #15672 |
@abdulrahuman5196 what amount do you think is fair? |
@luacmartins Hi, I am fine with any amount team thinks is fair for this. I don't have any specific request. I just felt we could re-evaluate based on the complexity involved. |
Since this isn't an issue rather than a feature request and improvement, no offending PR and checklist should be added.
We should update the current test case for invite members. I'll propose the regression step. |
Update for Manage Members - Invite TC
I also think we need to update Manage Members - Invite - Error test (Online/Offline) TC too, but I haven't got the time to add it. |
Hi team, When you are available, could you kindly check on this request? #15083 (comment) cc: @mallenexpensify |
Apologies for the delay @abdulrahuman5196. I'm not the most well-versed on the technical details. it's often best/easiest when you propose the amount then we can 👍, 👎 or propose another amount. The expected behavior was
It sounds like the amount of work that went into achieving that behavior required a lot more work than just a single bug fix. Based on the $2000 job amount, what percentage of additional work, outside of the single bug fix, do you think was necessary to get the PR deployed to production? Generally we default to 25, 50 and 100% when considering payment amounts. |
Thank you for response @mallenexpensify. I think 50% or 100% should be good in this case(Since time bonus is also not possible on this fix). 🎉 for 100% @luacmartins @thienlnam @mollfpr Kindly update your preference / thoughts |
@mallenexpensify I think that a 50% bonus seems fair in this case. |
@mallenexpensify As the team is agreeing on 50% bonus as a fair update in this case. cc: @luacmartins |
Thanks all. @abdulrahuman5196 @mollfpr , can you please accept the job and reply here once you have? https://www.upwork.com/jobs/~01478651038f1ade96 Reminder to add the $1000, 50% when paying :) |
@mallenexpensify Accepted, thank you! |
@mallenexpensify accepted the invite. |
Paid @mollfpr and @abdulrahuman5196 , thanks! TC GH created! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
User can see the list of his contacts without interference.
Actual Result:
When adding a new member to the workspace (using search), the user and search box is overlaid with keyboard. And also when scrolling up, the "Invite" button is hidden, which hides users from the list completely.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.70.1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen_Recording_20230211_164621_Chrome.mp4
Bug5934127_Screen_Recording_20230212_0043181_Chrome.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: