• 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      It has come to our attention that the current auto-close policy duration of 7 days may not be sufficient for all use-cases. Considering the varying needs of our diverse user base, we propose extending the maximum limit of the auto-close policy up to 31 days.

      This extension would provide greater flexibility in managing team alert policies across a wider range of projects and tasks. It would accommodate users requiring longer durations for their specific operational or project management needs.

      https://support.atlassian.com/opsgenie/docs/create-and-manage-team-alert-policies/#Notification-Policy

            [OPSGENIE-1621] Extend Auto-Close Policy Duration

            Dylan made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels New: cll-tf3202505

            Dylan added a comment -
            Atlassian Update - May 13, 2025

            Hi everyone,

            Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.

            In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management

            Dylan added a comment - Atlassian Update - May 13, 2025 Hi everyone, Thank you for bringing this Suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap . In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management
            SET Analytics Bot made changes -
            Support reference count New: 3
            Rafael Meira created issue -

              Unassigned Unassigned
              13c55fdaeda8 Rafael Meira
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: