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

Allow customers to view requests created by other customers belonging to the same organisation using the Customer Portal

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.

      As a result of -----JSD-62-----, customers will only be able to view and track their own requests using the Customer Portal.

      Using the feature proposed in -----JSD-269-----, it will be possible for customers to manually add request participants. However, it may be common for customers of a particular logical group (eg. organisation) to need to be granted default access view requests made by others from the same organisation.

      Users from the same organisation should be able view, search and comment on requests. Users from different organisations should not be able to view each others' requests.

       

      Update as of 3 Jan 2017

      Hello Server customers,

      Great news - Customer organization is now available on server! To find out more about this feature, check out our documentation here.

      On behalf of the JSD team I want to thank all of you for your patience. Your comments, feedback and interviews have all formed the feature update we release today.

      — JIRA Service Desk Team

       

      Update as of 28 Sep 2016

      Hi all,

      Great news! Customer organisation is now available on cloud! To find out more about this feature, check out our blog post and documentations here.

      This feature will also be available for Server in a future major server release.

      On top of this we have also built public APIs so you can easily extend our feature to support your various usecases! Check out our API docs here.

      On behalf of the JSD team I want to thank all of you for contributing to this ticket. Your comments, feedback and interviews have all formed the feature we release today.

      — JIRA Service Desk Team

       

      Update as of 15 Sep 2016

      Hi all,

      We are at the tail end of the development process for this feature. We are currently performing final testing as this feature touches on many sensitive parts of our products relating to permissions and security model.

      We also want to thank all of you who have joined us for the usability test, your feedback was very valuable and we have made a number of changes to the feature based on the feedback.

      As mentioned earlier, this feature will be available to both Cloud and Server and will be available on Cloud first before Server as there are far less permutations to test and QA on our Cloud infrastructure.

      Thank you all again for your patience.

      — JIRA Service Desk Team

       

      Update as of 21 Jul 2016

      Hi all,

      We do have a very vibrant marketplace which our expert partners develop add-ons that extend our products. Collection Issue View for Service Desk and Teams for JIRA Service Desk are both add-ons which aim to provide customer grouping capabilities for JSD Server. If you are on JSD Server you can evaluate these options and choose to purchase them if they meet your needs.

      As mentioned before this feature is one of our highest priorities and the JIRA Service Desk team is actively developing this capability. We are building it as a core part of the product, so there will not be any additional cost for this capability - and we are building it for both Server and Cloud.

      Unfortunately the development of this feature is taking considerable time as the security model for users in Cloud is very different to Server. It also fundamentally changes the way our product works so we want to ensure we get it right.

      If you are interested to see how the feature is progressing feel free to leave your details to join one of our upcoming usability test and provide us feedback on the feature itself.

      Thank you all again for your patience.

      — JIRA Service Desk Team

       

      Update as of 27 Jun 2016

      Hi all,

      This is one of our highest priorities and we have the best team working on the feature.

      This feature fundamentally changes the way our product work and we want to ensure we get it right. We have been actively reaching out to this community for usability testing on our latest development and design work on this feature. If you are keen to see where we are up to with the this feature, you can leave your details here to join one of our upcoming usability test and provide us feedback on the feature itself.

      Thank you all again for your patience.

      — JIRA Service Desk Team

       

      Update as of 3 May 2016

      Hey all,

      We understand many of you will need to make business decisions around when this feature is available, however we do not have a meaningful ETA we can share. As mentioned in my previous comment this is already in active development but there are quite a few number of moving parts to implementing this feature.

      We will do our best to keep everyone updated with the latest development regarding this feature and to share our designs/progress once they become available. Right now we are in the process of bringing in groups into JIRA Service Desk (Ability to add groups to tickets, JQL search for groups etc) and also making enhancements to the group infrastructure (Allowing agents to be managing groups etc).

      Again I want to stress this feature requires big changes to our underlying user management and permission infrastructure. Both of these aspects are fundamental to how you manage your users and the access control of the system, and we need to take the time to make sure we are doing it in the best possible way possible. Thank you again for all your continuous feedback and I will do my best to make progress updates as we go along.

      -JIRA Service Desk team

        1. Capture2.JPG
          Capture2.JPG
          30 kB
        2. screenshot-1.png
          screenshot-1.png
          261 kB
        3. screenshot-2.png
          screenshot-2.png
          264 kB
        4. scr-jira-sd-cc.png
          scr-jira-sd-cc.png
          31 kB

              edwin@atlassian.com edwin
              shamid@atlassian.com shihab
              Votes:
              1337 Vote for this issue
              Watchers:
              789 Start watching this issue

                Created:
                Updated:
                Resolved: