Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3333

URGENT - Auto Status Change Functionality Required

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • Automation
    • None
    • 1
    • 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.

    Description

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

      My organisation is currently in the process of migrating to JIRA Service Desk from our existing supplier, but one of the features that I am unable to identify within JIRA SD is the function to set the call status to automatically change on a given time/date. For example, a request is logged but doesn't need to start until two weeks later, therefore we change the call status to 'On-Hold', but then specify the time and date when we would like the call status to automatically change to 'Open'.

      This is an extremely important feature for us and would require this if we are to complete our migration. Could I request that this feature is added at your earliest possible convenience please. One possible way that I see this working in JIRA would be to add an Auto Status Change feature within a Workflow Transition. However, I'm still fairly new to this so you may be able to advise of another solution.

      I look forward to hearing from you.

      Many thanks
      Nathan

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cd36b8fbe389 Nathan Fletcher
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync