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

Missing "Cypress App Triage Board" #28653

Closed
MikeMcC399 opened this issue Jan 6, 2024 · 2 comments · Fixed by #28876
Closed

Missing "Cypress App Triage Board" #28653

MikeMcC399 opened this issue Jan 6, 2024 · 2 comments · Fixed by #28876

Comments

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Jan 6, 2024

Current behavior

Referring to the document cypress-prioritization-and-triage.md:

  1. the Cypress App Triage Board from the section The Cypress App Issue Triage is no longer accessible. The link returns a 404 error.

  2. The Cypress App Triage Process does not seem to be followed anymore and the label Stage: Under Development is undefined in the labels list for the repo.

Desired behavior

Align the document cypress-prioritization-and-triage.md with the current support process concerning submissions to the repo's issue list.

@MikeMcC399
Copy link
Contributor Author

@jennifer-shehane

Has the Cypress App Triage Board on https://github.com/orgs/cypress-io/projects/9/views/1 been removed deliberately or this is an oversight?

@MikeMcC399
Copy link
Contributor Author

MikeMcC399 commented Feb 6, 2024

@jennifer-shehane

README > "How we work" says:

How we work

At Cypress we value our community and strive to be as open and transparent with them as possible. Check out our guide on how we prioritize community issues.

now leads to

image

The original document also provided a link and explanation to "The Cypress App Priorities board shows the high-level roadmap at Cypress. " which is now missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant