-
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
Polish admins-only policy room feature #21950
Polish admins-only policy room feature #21950
Conversation
This reverts commit 823d28a.
…ture/21456-polish-admin-rooms
…ture/21456-polish-admin-rooms
…ture/21456-polish-admin-rooms
…ture/21456-polish-admin-rooms
…ture/21456-polish-admin-rooms
@shawnborton @mananjadhav One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
Seems good to me. One thing to consider though for a different PR, do we want all of the inputs on the create room flow to use our push-to-page pattern? cc @JmillsExpensify @trjExpensify for a gut check there |
@shawnborton Hi! Do I need an approve from you on this PR? |
This looks good to me, assuming we'll update the input style in a different PR. |
…ture/21456-polish-admin-rooms
@rezkiy37 there are conflicts now 😅 |
…ture/21456-polish-admin-rooms
Just fixed! |
@amyevans I did some testing and it works fine. Can you do a final review? I can then finish the checklist by uploading screencasts for all the platforms? |
@mananjadhav Done! |
Reviewer Checklist
Screenshots/VideosWebweb-policy-admin_UJauJnF3.mp4Mobile Web - Chromemweb-chrome-policy-admin.movMobile Web - Safarimweb-safari-policy-admin.movDesktopdesktop-policy-admin.moviOSios-policy-admin.movAndroidandroid-policy-admin.mov |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.46-0 🚀
|
🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.47-0 🚀
|
🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.46-2 🚀
|
@rezkiy37 @mananjadhav @amyevans due to incorrect mappings in |
@Pujan92, AFAIK, you already posted a proposal to fix it. Are you going to open a PR or should I do it? |
I can raise a PR but as it is in the regression period the author gets the first chance to raise it. |
Well, I am the author and will fix it. Okay? |
Sure 😅 , if it is considered and labeled as deployBlocker then maybe the team could have considered my proposal and assigned me to unblock deployment. |
🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.47-6 🚀
|
Details
Fixed Issues
$ #21456
PROPOSAL: #21456 (comment)
Tests
a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Run script "web" and open the web app. Obviously, you are able to run on any platform, but here we can easily debug.
c. Click on "+" (FAB menu).
d. Click on "New room".
e. Select a workspace, where you are an admin.
f. Verify that there is a new selector - "Who can post" with 2 values: "All members" and "Amins only".
g. Fill in all selectors/inputs as you want (up to you).
h. Open the "Network" tap of DevTools. Recommendations: select "XHR/Fetch" and "Preserve Log".
i. Click on "Create room".
j. Find a request ends "command=AddWorksapceRoom" and open "Payload" tap.
k. Verify that there is the
writeCapability
key and the value should be that you have selected: "All members" equalsall
and "Amins only" equalsadmins
.l. Repeat from the c step, but select the other value for the new selector.
a. Since, it is not a production feature yet, you should be invited to the policy room beta and assign task beta.
b. Run script "web" and open the web app. Obviously, you are able to run on any platform, but here we can easily debug.
c. You should be a member of any workspace where there are "admin-only" and "all members" posting rooms. Note: you should not be an admin for this workspace to test this improvement.
d. Click on "+" (FAB menu).
f. Click on "Assign task".
f. Fill in any text to "Title" and "Description", it is up to you.
g. Click on "Next".
h. Click on "Assign".
i. Verify that no "admin-only" rooms, because your are a member for the current workspace.
a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Run script "web" and open the web app. Obviously, you are able to run on any platform, but here we can easily debug.
c. You should be a member of any workspace where there are "admin-only" and "all members" posting rooms. Note: you should not be an admin for this workspace to test this improvement.
d. Open any "admin-only" posting room.
e. Verify that the distance between the bottom and the last message is shorter than on the staging or production.
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Run script "web" and open the web app. Obviously, you are able to run on any platform, but here we can easily debug.
c. Open any "admin-only" posting room.
d. Verify that the welcome message is a kind of: "Use <ROOM_NAME> to hear about important announcements related to <WORKSPACE_NAME>".
Offline tests
a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Open the app.
c. Enable the
offline
mode.d. Click on "+" (FAB menu).
e. Click on "New room".
f. Select a workspace, where you are an admin.
g. Verify that a new selector appears - "Who can post" with 2 values: "All members" and "Amins only".
h. Select any value for the new selector. Fill in the other selectors/inputs as you want (up to you).
i. Click on "Create room".
j. The app should redirect you to a new room chat page.
k. Open the chat settings and verify that it has the same values that you entered before.
l. Disable the
offline
mode.m. Repeat from the c step, but select the other value for the new selector.
QA Steps
a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Open the app.
c. Click on "+" (FAB menu).
d. Click on "New room".
e. Select a workspace, where you are an admin.
f. Verify that a new selector appears - "Who can post" with 2 values: "All members" and "Amins only".
g. Select any value for the new selector. Fill in the other selectors/inputs as you want (up to you).
h. Click on "Create room".
i. The app should redirect you to a new room chat page.
j. Open the chat settings and verify that it has the same values that you entered before.
k. Repeat from the c step, but select the other value for the new selector.
a. Since, it is not a production feature yet, you should be invited to the policy room beta and assign task beta.
b. Open the app.
c. You should be a member of any workspace where there are "admin-only" and "all members" posting rooms. Note: you should not be an admin for this workspace to test this improvement.
d. Click on "+" (FAB menu).
f. Click on "Assign task".
f. Fill in any text to "Title" and "Description", it is up to you.
g. Click on "Next".
h. Click on "Assign".
i. Verify that no "admin-only" rooms, because your are a member for the current workspace.
a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Open the app.
c. You should be a member of any workspace where there are "admin-only" and "all members" posting rooms. Note: you should not be an admin for this workspace to test this improvement.
d. Open any "admin-only" posting room.
e. Verify that the distance between the bottom and the last message is shorter than on the staging or production.
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.a. Since, it is not a production feature yet, you should be invited to the policy room beta.
b. Open the app.
c. Open any "admin-only" posting room.
d. Verify that the welcome message is a kind of: "Use <ROOM_NAME> to hear about important announcements related to <WORKSPACE_NAME>".
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Web
1.mov
2.mp4
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.Mobile Web - Chrome
Chrome.1.MP4
Chrome.2.MP4
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.Mobile Web - Safari
Mobile.Safari.1.MP4
Mobile.Safari.2.MP4
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.Desktop
Deskop.1.mov
Deskop.2.mov
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.iOS
IOS.1.mov
IOS.2.mov
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.Android
Android.1.mov
Android.2.mov
Use ${roomName} to hear about important announcements related to ${workspaceName}
for "admin-only" rooms.