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

Add Customer Organizations to JIRA Service Desk Server

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.

      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 7th Nov

      Hi all,

      Thanks for all your comments, as mentioned in the other ticket (--JSD-270--) this feature is indeed coming to JSD Server in the next major release. We typically have a major server release very 3-5 months and our last major server release (3.2) was in August so it should be available soon.

      The feature will be identical to the one available on cloud right now and I will provide an update again when the server release is out.

      Thanks,
      JIRA Service Desk team

       

      --JSD-270-- introduced customer organizations to cloud. This is a suggestion to add customer organizations to the server version of JIRA Service Desk.

      This suggestion is also known as "Allow customers to view requests created by other customers belonging to the same organisation using the Customer Portal" as well as "Customer Groups" or "Grouping Customers"

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              214 Vote for this issue
              Watchers:
              184 Start watching this issue

                Created:
                Updated:
                Resolved: