Skip to content
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

Create onboarding UXR issues #2974

Open
4 of 6 tasks
sacamp opened this issue Mar 13, 2022 · 13 comments
Open
4 of 6 tasks

Create onboarding UXR issues #2974

sacamp opened this issue Mar 13, 2022 · 13 comments
Labels
Complexity: Missing feature: research plan any issue that is specifically about the overall research, not a subtask feature: research Research: RP001 Volunteer Onboarding Research role: user research size: 1pt Can be done in 4-6 hours

Comments

@sacamp
Copy link
Contributor

sacamp commented Mar 13, 2022

Overview

We need to create issues from the Action Steps spreadsheet that was generated from the onboarding research project. This will enable the continuation of UX research based on the insights generated from previous research.

Action Items

  • Review the Creating and Working with GitHub Issues for how to create issues
  • Review the onboarding research summary slide deck
  • Review the action steps spreadsheet
  • Create issues from action items that have "UX" under the "Responsible" column (in spreadsheet) using the guidance from Creating and Working with GitHub Issues
  • update the wiki with issue numbers
  • Review issues with research lead to get them to sign off and have them add ready for milestone label

Resources/Instructions

@sacamp sacamp added role: user research Ready for Prioritization feature: research plan any issue that is specifically about the overall research, not a subtask size: 1pt Can be done in 4-6 hours labels Mar 13, 2022
@github-actions
Copy link

Hi @sacamp.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

@sherririllingux sherririllingux self-assigned this Mar 18, 2022
@Providence-o Providence-o added this to the 08. Team workflow milestone Mar 20, 2022
@github-actions github-actions bot added the To Update ! No update has been provided label Mar 25, 2022
@sherririllingux
Copy link
Member

sherririllingux commented Mar 25, 2022

Currently finished with first of four issues. Should be completed with all four by the end of the weekend.

#3003

@sherririllingux sherririllingux added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided labels Mar 25, 2022
@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Apr 8, 2022
@sherririllingux sherririllingux removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Apr 10, 2022
@sherririllingux
Copy link
Member

I have added a comment in issue #3005 and issue #3011 on what I'm working on and researching. I'm currently trying to figure out what data backs up the need for these issues. I haven't found anything that constitutes an issue for each, but I'm waiting on access to Google Docs and Miro to research some more. Will update once I have access.

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Apr 15, 2022
@sherririllingux
Copy link
Member

I'm currently working on the issue from the action steps that is asking for a self-quiz to determine where new volunteers should be placed based on their goals, experience, and skills. It is issue #3005.

@hackforla hackforla deleted a comment from github-actions bot Apr 29, 2022
@hackforla hackforla deleted a comment from github-actions bot Apr 29, 2022
@hackforla hackforla deleted a comment from github-actions bot Apr 29, 2022
@hackforla hackforla deleted a comment from github-actions bot Apr 29, 2022
@sacamp sacamp removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 4, 2022
@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label May 6, 2022
@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label May 13, 2022
@github-actions
Copy link

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, May 10, 2022 at 12:23 AM PST.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 13, 2022
@sherririllingux
Copy link
Member

I am currently working on some revisions of the Onboarding quiz. Should be done by the end of the week for review.

@ExperimentsInHonesty ExperimentsInHonesty removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 18, 2022
@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed Status: Updated No blockers and update is ready for review labels May 20, 2022
@github-actions
Copy link

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, May 24, 2022 at 12:21 AM PST.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 27, 2022
@sherririllingux
Copy link
Member

Finishing up the revision that Bonnie and Simone suggested and will be sending link to Simone tonight.

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Jun 3, 2022
@sherririllingux
Copy link
Member

I sent revisions for onboarding quiz to Simone to look over and advise if more revisions are needed.

@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jun 17, 2022
@github-actions
Copy link

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, June 14, 2022 at 12:19 AM PST.

@github-actions
Copy link

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, June 21, 2022 at 12:20 AM PST.

@github-actions
Copy link

github-actions bot commented Jul 1, 2022

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, June 28, 2022 at 12:21 AM PST.

@github-actions
Copy link

github-actions bot commented Jul 8, 2022

@sherririllingux

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, July 5, 2022 at 12:19 AM PST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing feature: research plan any issue that is specifically about the overall research, not a subtask feature: research Research: RP001 Volunteer Onboarding Research role: user research size: 1pt Can be done in 4-6 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

5 participants