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

As a JSD customer, I would like to add participants to just watch issues (Without the ability to create new issues)

XMLWordPrintable

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

      As a JIRA Service Desk customer, it would be nice if you could have an option on the "Add People/Participants" button where you can choose if the new participant will only have the permissions to just watch issues (read-only access) without the service desk customer standard permissions (e.g Those new participants can not create new issues on the customer portal).

            [JSDSERVER-2067] As a JSD customer, I would like to add participants to just watch issues (Without the ability to create new issues)

            Charlie Marriott added a comment -
            Atlassian Update – 19 Feb 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 – 19 Feb 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

            bede added a comment -

            We got the same requirements from our larger (corporate) customers, who want to let their subsidiary users in on requests they set out with us for them.

             

            So typically a case of our corporate customer organizes 1st line support within their corporation, only when they can't solve an issue themselves, the HQ will raise a request on our portal. 
            they want the local users to be able to view the issue + add a comment, but prevent the local users from creating new request in the portal, or change the sharing on an existing request (add/remove users/organizations)

             

            Currently, we workaround the creation limitation via a validator on the "create issue" transition in underlying workflow, but this approach would be better handled via portal, e.g. via:

             Split-up the Role "Customer-users" into "Portal-access users" and "Portal Request creators/editors"

             

             

             

            bede added a comment - We got the same requirements from our larger (corporate) customers, who want to let their subsidiary users in on requests they set out with us for them.   So typically a case of our corporate customer organizes 1st line support within their corporation, only when they can't solve an issue themselves, the HQ will raise a request on our portal.  they want the local users to be able to view the issue + add a comment, but prevent the local users from creating new request in the portal, or change the sharing on an existing request (add/remove users/organizations)   Currently, we workaround the creation limitation via a validator on the "create issue" transition in underlying workflow, but this approach would be better handled via portal, e.g. via:  Split-up the Role "Customer-users" into "Portal-access users" and "Portal Request creators/editors"      

            Srinivas Srikanta added a comment -

            We have the same scenario in our organization.

            Srinivas Srikanta added a comment - We have the same scenario in our organization.

            Maria Burrows added a comment -

            This is a requirement for us. We need the ability to have organisations customers able to view the tickets within an organization but not be able to create tickets in the organization.

            regards
            Maria.

            Maria Burrows added a comment - This is a requirement for us. We need the ability to have organisations customers able to view the tickets within an organization but not be able to create tickets in the organization. regards Maria.

              Unassigned Unassigned
              pahennig Paulo Hennig (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: