You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if anyone has found themselves in a similar position as our team.
In our team's usage of maintenance tasks we found that with the additions of new tasks, and previous runs displaying raw data it made it difficult to find specific tasks.
I've put up a PR for a proposed feature addition. Would love to get some thoughts on it, or any suggestions on how to mitigate this issue.
There's a way in Ruby to group things classes: using modules as namespaces. We properly support nesting since #809, maybe we could give a way to filter by module instead of adding the concept of tag?
For example, /maintenance_tasks/ could continue showing all tasks as it does today, but for projects using modules nested under Maintenance, we could list their names at the top of the index, allowing to filter tasks by module.
That would be definitely preferred. We did notice that it was nice that we could have the nested structure, but saw no benefit to it since it didn't help with the ability to filter. I can take a look at making some changes in my PR to reflect that.
This issue has been marked as stale because it has not been commented on in two months.
Please reply in order to keep the issue open. Otherwise, it will close in 14 days.
Thank you for contributing!
Hello!
I am wondering if anyone has found themselves in a similar position as our team.
In our team's usage of maintenance tasks we found that with the additions of new tasks, and previous runs displaying raw data it made it difficult to find specific tasks.
I've put up a PR for a proposed feature addition. Would love to get some thoughts on it, or any suggestions on how to mitigate this issue.
#815
Thanks!
The text was updated successfully, but these errors were encountered: