Make transition_after_days configurable

[Kjoep]

Problem Statement

In our team, we strongly rely on the review list (for_review filter) to handle incoming issues (new or regressed). When someone looks into an issue, they either log it to the bug tracker or takes other actions to make sure it will get resolved, and then mark it as reviewed. That way the list functions as a todo list for the team.

The fact that issues leave the for_review list after 7 days is problematic for us, because it can happen, if we're swamped, that we lose track of issues this way. We would like to be able to configure this behaviour (turn it off or make it occur later).

Solution Brainstorm

No response

Product Area

Unknown

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[mrduncan]

Hi @Kjoep, we recently launched Issue Views which are much more flexible ways to share these types of queues with others in your organization. You'll just need to opt into the new navigation to access them (https://sentry.io/changelog/new-nav-issue-views-ga/).

https://docs.sentry.io/concepts/search/searchable-properties/ has the full list of searchable properties but, based on your description something like is:unresolved !is:linked might be a good start (unresolved and doesn't have a link to an external issue tracker).

I'm going to close this for now as this isn't a configuration option we plan on supporting now that users can build much more configurable issue views.