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

      It seems that Organizations could be a very powerful tool in Jira ServiceDesk but it's lacking several fundamental features that could make it really work:

      1. Allow on the customer record to show the organization. Right now when we search customer we have no idea if they actually have the organization tied to them. You have to search in two places. 
      2. Allow to default an organization for a customer since you can have more than 1 organization per customer. This way when they submit via email or the portal a ticket it will populate an organization by default.
      3. Have an admin setting to turn off allowing customers to NOT share with their organization. We have an issue where users see this in the portal and decide not to share it and we have to update them when coming in. Which is difficult because when you search for the customer it doesn't house the organization at their record (see #1).
      4. Allow for Organizations to be shared across the Jira platform. We use Software and now have to create a separate field to capture the organization of our Reporter. 

        1. 70-480-dumps.pdf
          3.05 MB
        2. 70-487-dumps.pdf
          5.65 MB

            [JSDCLOUD-8096] Organization Settings

            Liron added a comment -

            Hi Danielle,

            Part of this ticket is in fact a duplicate of another ticket we just recently shipped and resolved, https://jira.atlassian.com/browse/JSDCLOUD-4382

            The other parts of the ticket are currently not being considered, but please stay tuned in case plans change in the coming months, we will update on this ticket.

            Thank you

            Liron

            Jira Service Management team

            Liron added a comment - Hi Danielle, Part of this ticket is in fact a duplicate of another ticket we just recently shipped and resolved, https://jira.atlassian.com/browse/JSDCLOUD-4382 .  The other parts of the ticket are currently not being considered, but please stay tuned in case plans change in the coming months, we will update on this ticket. Thank you Liron Jira Service Management team

            I Agree..We have given up looking to migrate to JSD becuase the Organziational fields are not carried onto each ticket. This is BASIC for a ticketing system. When an agent takes a ticket, not only do they need to see what the customer (human) wants/need, they also need to see the organization they work for and the relationship - what SLA, which site (address), Is there a partner?, etc...if those takes arent copied onto each ticket the ticket is half useless.

             

            Scott Goldman added a comment - I Agree..We have given up looking to migrate to JSD becuase the Organziational fields are not carried onto each ticket. This is BASIC for a ticketing system. When an agent takes a ticket, not only do they need to see what the customer (human) wants/need, they also need to see the organization they work for and the relationship - what SLA, which site (address), Is there a partner?, etc...if those takes arent copied onto each ticket the ticket is half useless.  

              ldeutsch Liron
              f057210b1519 Danielle Mather
              Votes:
              9 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: