-
Notifications
You must be signed in to change notification settings - Fork 69
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
Improve the logic and functionality used by the "featured" fields on Stories #1317
Comments
sorry, accidentally removed the sprint 50 label from this one, then put it back |
Note for when Events gets more priority: PR #6766 is open, with comment:
& Note from Kev that the help text needs a content edit. |
This could be either a Public Websites issue or a Facilities Issue. It is most likely a Facilities issue to tackle only because they are by far the biggest user of the "featured" aspect. |
@JayDarnell I am adding the defect label because right now the "featured" aspect does not work the way anyone expects it to work and does not work the way the help text says it should work. |
New occurrence of how this is now affecting Lovell: https://dsva.slack.com/archives/C0FQSS30V/p1683224452110549 |
We will not standardize this behavior, as the old mechanism for Featuring will be retired from Events entirely, and re-envisioned for Stories. Facilities owns the task moving forward, which may use an entirely different re-envisioned functionality. Leaving ticket open, and it may / should probably move to the new Facilities epic for Future state, when it is opened. |
Closing as duplicate of #13695 |
Background
ACs
The text was updated successfully, but these errors were encountered: