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

As an Agent, I would like to allow some fields to be editable by customers who created/participated a ticket

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Customer Portal
    • 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.

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

      Problem Definition

      Today, Service Desk Customers do not have the ability to edit an issue once it's created. There are times when the creator or the participants (Service Desk Customers) want to edit the Summary, Description, Priority or etc but they couldn't.

      Suggested Solution

      Allow fields to be configurable to be editable by the creator or the participants (Service Desk Customers)

      • Summary
      • Description
      • Priority
      • Link issue (Suggestion should be disabled due to security reason)

          Form Name

            [JSDSERVER-4011] As an Agent, I would like to allow some fields to be editable by customers who created/participated a ticket

            Charlie Marriott made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Atlassian Update – 6 July 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,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 6 July 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, Charlie Jira Service Management, Server & Data Center
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011971 ] New: JAC Suggestion Workflow 3 [ 3649523 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665589 ] New: JAC Suggestion Workflow [ 3011971 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2323833 ] New: Confluence Workflow - Public Facing v4 [ 2665589 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052473 ] New: JSD Suggestion Workflow - TEMP [ 2323833 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2047723 ] New: JSD Suggestion Workflow [ 2052473 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1426231 ] New: JSD Suggestion Workflow - TEMP [ 2047723 ]
            jonah (Inactive) made changes -
            Description Original: h3. Problem Definition
            Today, Service Desk Customers do not have the ability to edit an issue once it's created. There are times when the creator or the participants (Service Desk Customers) want to edit the Summary, Description, Priority or etc but they couldn't.

            h3. Suggested Solution
            Allow fields to be configurable to be editable by the creator or the participants (Service Desk Customers)
            * Summary
            * Description
            * Priority
            * Link issue (Suggestion should be disabled due to security reason)
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4011].
              {panel}

            h3. Problem Definition
            Today, Service Desk Customers do not have the ability to edit an issue once it's created. There are times when the creator or the participants (Service Desk Customers) want to edit the Summary, Description, Priority or etc but they couldn't.

            h3. Suggested Solution
            Allow fields to be configurable to be editable by the creator or the participants (Service Desk Customers)
            * Summary
            * Description
            * Priority
            * Link issue (Suggestion should be disabled due to security reason)

              Unassigned Unassigned
              a.demesquita Ryan Debattista
              Votes:
              9 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: