Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-2934

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

XMLWordPrintable

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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.

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

            Matthew Hunter added a comment -
            Atlassian Update - December 1, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - December 1, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Ewin Davis K (Inactive) added a comment -

            We looked at this feature request and we have decided to not pursue this yet in the near future. We will continue to monitor the feedback and re-evaluate if we have significant customer interest.

            Ewin Davis K (Inactive) added a comment - We looked at this feature request and we have decided to not pursue this yet in the near future. We will continue to monitor the feedback and re-evaluate if we have significant customer interest.

              d0d1ba410583 Sushant Koshy
              4e81381d415c Tim Eddelbüttel
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: