• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • SLA
    • None
    • 0
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Problem definition and suggested resolution

      Currently, the calendar for the SLA's is configured to be set in a weekly/monthly basis. It will be nice if the user is given the ability to configure those settings on a seasonal basis, in order to define specific working hours for the specific period in year.

      The reason behind that is that some companies working hours differs depending on seasons. And it will make it much easier to make the calendar configurable based on the seasons.

      Workaround

      1. Define new calendar, with different working hours and holidays (if any).
      2. Modify existing SLA and add new targets to cover seasonal dates: specify applied create dates in JQL, then select modified newly added calendar. For example, if we want to apply changed calendar between dates 6th May 2019 until and including 6th June 2019 (date format depends on the used date format on Jira instance):
        issuetype = Incident and (createdDate >= "2019-05-06" and createdDate < "2019-06-07")	

        • Make sure these exceptional SLA targets are located above other targets, so that they get applied first when SLA selection has been triggered and if several targets are matched.
      3. After the SLA has been saved, it will get applied to existing issues that fall into the specified interval.

            [JSDSERVER-212] Periodic Calendar for SLA's

            Atlassian Update – 19 Feb 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 19 Feb 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              aalshargabi AlaA
              Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: