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

Allow customers to edit the priority of an existing issue

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Customer Portal
    • None
    • 3
    • 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 customers create issues via the portal and email. There are scenarios where the customer wants to change the priority. Today they can only request this by submitting a comment and hoping that the agent acts on it. We have rules/automation that result in escalation notification if priority is set to Urgent/Highest. If the agent doesn't act on, or does so in a delayed manner, then the notification does not occur or is delayed.

      There may be a workaround here though ugly (I need to test this). Transitions could be created in the workflow for each priority level setting the transition from "All". Then expose each of these transitions on the portal. The customer could then click on the transitions, e.g.

      • Priority = Highest
      • Priority = High
      • Priority = Medium
      • Priority = Low
      • Priority = Lowest

      again...yuck!

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              075ebb79f6aa Jack Brickey
              Votes:
              57 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:

                Backbone Issue Sync