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

ER: fix the name of Capitalization of one of the meetings on the events page #6278

Closed
4 tasks
ExperimentsInHonesty opened this issue Feb 11, 2024 · 1 comment
Closed
4 tasks
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request P-Feature: Wins Page https://www.hackforla.org/wins/ role: product Product Management size: 0.25pt Can be done in 0.5 to 1.5 hours waiting on stakeholder

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 11, 2024

Emergent Requirement - Problem

image

We need to Log into VRMS and change the COMMUNITY OF PRACTICE: CoP Leads and its link https://www.hackforla.org/events/undefined) to the correct info (see resources section below)

Issue you discovered this emergent requirement in

Date discovered

2024-01-29

Did you have to do something temporarily

  • YES
  • [x ] NO

Who was involved

@ExperimentsInHonesty @JessicaLucindaCheng @roslynwythe

What happens if this is not addressed

It's currently listed on the Events page and then takes people to a 404 link.

Resources

Content to update

Project Name

Community of Practice: CoP Leads

Project Description

The Leads Meeting for All the CoPs

GitHub Identifier

337874660

GitHub URL

https://github.com/hackforla/communities-of-practice

​Slack Channel Link

https://hackforla.slack.com/archives/C026UMZK89X

​Google Drive URL

https://drive.google.com

HFLA Website URL

https://www.hackforla.org/communities-of-practice

Partners

  • none

Managed by Users

  • none

​#### Project Status

Active

Google Drive ID

https://drive.google.com/drive/folders/1MfC9chrrPozQZsq02wBzXjDsQKpoPz7_
VRMS Screenshot

screencapture-vrms-io-projects-64f740007211620022f7757d-2024-02-11-09_54_41

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

I messaged VRMS team in their slack with this content on 2024-02-11

Hi VRMS team.... I am sure there is an issue for this which
@Jack Haeger
can attach to this comment thread. But I want to communicate to the whole team, that VRMS is working software. Meaning people at Hack for LA rely on its functions. Its no ok to roll out changes to a feature in the live environment without testing it in dev with the user. X number of weeks ago, a change was made to the Meeting Setup/Edit page, which made some fields that we might not have data for, required (e.g., partners, Managed by Users, etc.). This means, I cannot make updates to any projects since the change. This is a problem that needs an urgent fix.
But the point here is not that you all put out this fire, which I do want you to do, but that you don't create new fires in the future. If you plan to change an existing feature, that will require close coordination with the users. Right now, I can be a stand in for all users. But things should still be coordinated with me so that the tool doesn't suddenly become unusable
tldr;
Please remove the required flag from Partners and Users in the project data.
Don't make changes to existing features without testing them with users in dev.

@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours ER Emergent Request role missing Complexity: Missing Draft Issue is still in the process of being created labels Feb 11, 2024
@ExperimentsInHonesty ExperimentsInHonesty self-assigned this Feb 11, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for product P-Feature: Wins Page https://www.hackforla.org/wins/ role: product Product Management Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. Draft Issue is still in the process of being created role missing Complexity: Missing labels Feb 11, 2024
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Feb 12, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request P-Feature: Wins Page https://www.hackforla.org/wins/ role: product Product Management size: 0.25pt Can be done in 0.5 to 1.5 hours waiting on stakeholder
Projects
Development

No branches or pull requests

1 participant