• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 3.4.2, 4.5.1, 4.13.1
    • Customer Organisation

      Steps to Reproduce:

      1. Create a Service Desk project "IT Service Desk"
      2. Create several requests in the project
      3. Create an Organization called "A"
      4. Login as a user that has "Service Desk Team" role of Project ISD but, it does not have the JSD license.
      5. Navigate to Issue Navigator via Issues > Search for Issues
      6. Change to "Advance" search.
      7. Put the JQL search below:
        project = ISD
      8. The issue coming from ISD projects will be listed.
      9. Add more condition on the search like below:
        project = ISD AND Organizations = "A"

      Expected Result:

      • No issue will be listed as there is no request raised under the "A" organization.

      Actual Result:

      • This comes out instead where the Collaborator should be able to view Organization value.

      Notes:

      1. With AutoComplete works when searching for Organization means that they are able to view the values.
      2. The collaborator itself able to view the ticket from the project without the column being defined in the search.

            [JSDSERVER-5085] Collaborators could not search with "Organization" field

            Closing this bug as this is by design. Currently an agent license is required to use Organisation in JQL.

            Please vote on the related Feature request https://jira.atlassian.com/browse/JSDSERVER-4873 if you would like this feature implemented.

            Benjamin Suess added a comment - Closing this bug as this is by design. Currently an agent license is required to use Organisation in JQL. Please vote on the related Feature request https://jira.atlassian.com/browse/JSDSERVER-4873 if you would like this feature implemented.

            VVor added a comment - - edited

            Welcome me to your society of fallen hopes, guys!

            I've already walked through the raising of a support request, as Renan advised.

            And now I'm here - on the page of 3yo BUG with a minor severity...

            I'm absolutely agree with Gavin's comment, which he wrote here in far 2017th - it's a "sucks".

            The company I'm working for is never turn their back to clients as Atlassian does. (I've checked - we have only 426 bug tickets with Declined/Won't Do resolution of total 100.000+ bug tickets -> less that 4%).

            And with this point of view they are dragging us into the annualy paid Datacenter edition with THE SAME policy of bug fixing. (off course everybody understand that this bug is still not fixed in DC for it's huge price)

             

             

            VVor added a comment - - edited Welcome me to your society of fallen hopes, guys! I've already walked through the raising of a support request, as Renan advised. And now I'm here - on the page of 3yo BUG with a minor severity... I'm absolutely agree with Gavin's comment, which he wrote here in far 2017th - it's a "sucks". The company I'm working for is never turn their back to clients as Atlassian does. (I've checked - we have only 426 bug tickets with Declined/Won't Do resolution of total 100.000+ bug tickets -> less that 4%). And with this point of view they are dragging us into the annualy paid Datacenter edition with THE SAME policy of bug fixing. (off course everybody understand that this bug is still not fixed in DC for it's huge price)    

            Renan Castro (Inactive) added a comment - https://getsupport.atlassian.com/browse/GHS-218893

            Hey, almost four years. Any news?

            For agents this works but for collaborators not. And that's very strange as collaborators can anyway see issues and what the organization is. Just cannot use that as a parameter in JQL for dashboard.

            Jarno Ahola added a comment - Hey, almost four years. Any news? For agents this works but for collaborators not. And that's very strange as collaborators can anyway see issues and what the organization is. Just cannot use that as a parameter in JQL for dashboard.

            I created a dashboard for sales, engineering, and management to monitor open issues for a specific organization but the dashboard is not viewable to those that do not have a JIRA Service Desk license because the dashboard is based on a filter that uses Organizations in the JQL. sucks

            Gavin Means added a comment - I created a dashboard for sales, engineering, and management to monitor open issues for a specific organization but the dashboard is not viewable to those that do not have a JIRA Service Desk license because the dashboard is based on a filter that uses Organizations in the JQL. sucks

            This bug is really annoying for collaborators. We cannot give them a Service Desk licence (number of agents is limited).

            fdo_orchestranetworks added a comment - This bug is really annoying for collaborators. We cannot give them a Service Desk licence (number of agents is limited).

              c8bcca445054 Benjamin Suess
              jrahmadiputra Julian (Inactive)
              Affected customers:
              47 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: