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

Ability to create your own custom field from the same type as request participants

XMLWordPrintable

    • 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.

      The custom field request participants has the same functionality like Cc in emails.

      In our service desk configuration we have some request types where the customer needs to enter their direct manager (e.g. extend file server permissions, get a license for a commercial software, ...).

      Due to the restriction that only agents can comment to the customer (reporter) a default JIRA user picker will not work in this scenario. Every other user than agents also request participants can only write internal comments if the comment is not written via the customer portal.

      Also the manager will not see the requests of his team within his customer portal.

      Additional add a permission type for this field so that it can be used in issue security levels or notification schemes.

            [JSDSERVER-2934] Ability to create your own custom field from the same type as request participants

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Charlie Marriott added a comment -
            Atlassian Update – 18 Jan 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 – 18 Jan 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
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011698 ] New: JAC Suggestion Workflow 3 [ 3649222 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665021 ] New: JAC Suggestion Workflow [ 3011698 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2322213 ] New: Confluence Workflow - Public Facing v4 [ 2665021 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052631 ] New: JSD Suggestion Workflow - TEMP [ 2322213 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048468 ] New: JSD Suggestion Workflow [ 2052631 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280501 ] New: JSD Suggestion Workflow - TEMP [ 2048468 ]
            jonah (Inactive) made changes -
            Description Original: The custom field _request participants_ has the same functionality like Cc in emails.

            In our service desk configuration we have some request types where the customer needs to enter their direct manager (e.g. extend file server permissions, get a license for a commercial software, ...).

            Due to the restriction that only _agents_ can comment to the customer (reporter) a default JIRA user picker will not work in this scenario. Every other user than agents also request participants can only write internal comments if the comment is not written via the customer portal.

            Also the manager will not see the requests of his team within his customer portal.

            Additional add a permission type for this field so that it can be used in issue security levels or notification schemes.             		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-2934].
              {panel}

            The custom field _request participants_ has the same functionality like Cc in emails.

            In our service desk configuration we have some request types where the customer needs to enter their direct manager (e.g. extend file server permissions, get a license for a commercial software, ...).

            Due to the restriction that only _agents_ can comment to the customer (reporter) a default JIRA user picker will not work in this scenario. Every other user than agents also request participants can only write internal comments if the comment is not written via the customer portal.

            Also the manager will not see the requests of his team within his customer portal.

            Additional add a permission type for this field so that it can be used in issue security levels or notification schemes.

              Unassigned Unassigned
              4e81381d415c Tim Eddelbüttel
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: