Skip to content

Conversation

kalikiana
Copy link
Member

To cover tickets without an assignee explicitly

To cover tickets without an assignee explicitly
Copy link
Member

@okurz okurz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to not have this on our status board as it would always alert us at the time of notification. Our status board should only show the status after we had sufficient time to prevent it showing an alert

@kalikiana
Copy link
Member Author

I would prefer to not have this on our status board as it would always alert us at the time of notification. Our status board should only show the status after we had sufficient time to prevent it showing an alert

How is that different to the untriaged queries? They also trigger immediately.

We could use updated conditions for all of these. Otherwise to be consistent we need to move these somewhere else 🤔 Personally I've found these very useful to have, though.

@okurz
Copy link
Member

okurz commented Apr 3, 2025

I would prefer to not have this on our status board as it would always alert us at the time of notification. Our status board should only show the status after we had sufficient time to prevent it showing an alert

How is that different to the untriaged queries? They also trigger immediately.

We could use updated conditions for all of these.

Oh, yes. Good point. We can have another query with the same parameters plus looking at the update time if it's more than a day (as I think granularity is 1 day)

@kalikiana
Copy link
Member Author

Oh, yes. Good point. We can have another query with the same parameters plus looking at the update time if it's more than a day (as I think granularity is 1 day)

Well, if we only use them here there's no need to duplicate everything. So I went ahead and updated them accordingly.

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 this pull request may close these issues.

4 participants