Share with field is not automatically populated - User is now required to take an extra step and select a value

XMLWordPrintable

    • 8
    • Severity 3 - Minor
    • 1

      Issue Summary

      As per JSDCLOUD-4382, Admins can change the default Organization sharing behavior by going to Settings > Products > Configuration (under Jira Service Management), within the "Organization management" section.

      When the value is set to be No, the Share with field used to automatically be populated with 'No one' and when the value was set to be Yes, the Share with field used to be automatically populated with the organization (As long as user was part of one organization)

      However this does not appear to be happening anymore.

      The Share with field is set to blank and user has to select a value.

      Steps to Reproduce

      1. Select "No, don't share email requests with the customer's organization. Requests sent from the portal will not be shared unless the customer selects otherwise" - as shown above in the screenshot
      2. As a customer belonging to one organization, create a ticket from the portal.
      3. Share with field should be automatically populated with 'No one'. - this does not happen
      4. Select "Yes, automatically share email requests with the customer's organization. Requests sent from the portal will also be shared unless the customer selects otherwise", to automatically share with organization
      5. As a customer belonging to one organization, create a ticket from the portal.
      6. Share with field should be automatically populated with the organization customer belongs to. - this does not happen

      Expected Results

      Share with field should be automatically populated based on the value selected in 

      Settings > Products > Configuration (under Jira Service Management), within the "Organization management" section.

      Actual Results

      Share with field is not automatically populated based on the value selected in 

      Settings > Products > Configuration (under Jira Service Management), within the "Organization management" section.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Pulkit Gupta (Inactive)
            Reporter:
            Bhaargavi Natarajan
            Votes:
            5 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: