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

Keep history of matching versions and actions for automation rules #6393

Closed
1 task
stsewd opened this issue Nov 19, 2019 · 0 comments · Fixed by #7658
Closed
1 task

Keep history of matching versions and actions for automation rules #6393

stsewd opened this issue Nov 19, 2019 · 0 comments · Fixed by #7658
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@stsewd
Copy link
Member

stsewd commented Nov 19, 2019

Right now users can see "that something is happening" or the if the rules is working as expected by looking at the builds or versions tab. Having just one place to see this would be great. Maybe something like we do with integrations.

  • Include a count and (truncated?) list of versions that match the current rule -- maybe in the listing page, but having a live reload list on the edit page would be the most useful.
@stsewd stsewd added Feature New feature Needed: design decision A core team decision is required labels Nov 19, 2019
stsewd added a commit that referenced this issue Nov 10, 2020
stsewd added a commit that referenced this issue Nov 10, 2020
stsewd added a commit that referenced this issue Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant