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

      Since Service Desk 3.1.x filter options have become available in the "My Request" section:

      1. Created by me
      2. Where I am a perticipant
      3. Created by anyone

      The "Created by anyone" filter shows all issues where the current user is the reporter or is added as participant. The filtername however suggests that this shows all issues within the Service Desk regardless of the reporter.
      This can cause confusion.
      Changing the name to something that reflects the actual outcome better could prevent this confusion.
      A suggestion could be to change this to "all visible requests" or something along those lines.

            [JSDSERVER-3528] Change the "Created by anyone" filtername under My Request

            This choice of words is confusing to users. Please make this configurable or chose a different words to describe the views. 

            Alicia Power added a comment - This choice of words is confusing to users. Please make this configurable or chose a different words to describe the views. 

            +1 You are all too kind on this one.

            Anything an issue reporter sees "in the portal" should have a configurable label.  As is, virtual nothing in the portal interface can be customized.  Please fix this by making it configurable – it's a no brainer.  Thank you.

            Stephen Wiggs added a comment - +1 You are all too kind on this one. Anything an issue reporter sees "in the portal" should have a configurable label.  As is, virtual nothing in the portal interface can be customized.  Please fix this by making it configurable – it's a no brainer.  Thank you.

            +1 vote. We have customers that need to see eachother issues as they work in same team or work with eachother, so I need that user can see issues 'created by anyone'.

            Also we have monthly meetings with our customers and would be great if customers can see all issues so we can talk about all issues during our meetings. In meetings would be great if same team customers can see eachother issues. 

            Martin Amor added a comment - +1 vote. We have customers that need to see eachother issues as they work in same team or work with eachother, so I need that user can see issues 'created by anyone'. Also we have monthly meetings with our customers and would be great if customers can see all issues so we can talk about all issues during our meetings. In meetings would be great if same team customers can see eachother issues. 

            +1 this has confused me for some time. I'd actually really like the option for users to be able to see issues CREATED BY ANYONE

            Lisa Hickley added a comment - +1 this has confused me for some time. I'd actually really like the option for users to be able to see issues CREATED BY ANYONE

            Andy Buck added a comment -

            How much more interest needs to be gathered to get this resolved?  This is terrible that I have to explain to each new service desk user what that means to alleviate the confusion this causes.

            Andy Buck added a comment - How much more interest needs to be gathered to get this resolved?  This is terrible that I have to explain to each new service desk user what that means to alleviate the confusion this causes.

            Voted +1 for this. Annoying choice of words as is generating queries from customer base when they cannot see 'all requests'. At the very least it should be able to be toggled on or off as not everyone will want this functionality.

            Chris Evans added a comment - Voted +1 for this. Annoying choice of words as is generating queries from customer base when they cannot see 'all requests'. At the very least it should be able to be toggled on or off as not everyone will want this functionality.

            I totally agree. When our customers see that phrase, they will think "Can anyone read my confidential information". This is definitely not good!

            John Walker added a comment - I totally agree. When our customers see that phrase, they will think "Can anyone read my confidential information". This is definitely not good!

            Ben Lawlor added a comment -

            I'll add a vote to have this addressed, as our Service Desk agents are misled when this dropdown is selected, thinking there is a configuration setup issue in our specific instance. 

            Ben Lawlor added a comment - I'll add a vote to have this addressed, as our Service Desk agents are misled when this dropdown is selected, thinking there is a configuration setup issue in our specific instance. 

            CSA RIS added a comment -

            I agree that the language "Created by anyone" does not match what is observed. Only issues where currentUser() is the reporter or among participants appear.

            Ideally, the issue filter (JQL) used by the My Requests view should be configurable. I want to let my customers really see issues "Created by anyone", but I can't do that at this time.

            CSA RIS added a comment - I agree that the language "Created by anyone" does not match what is observed. Only issues where currentUser() is the reporter or among participants appear. Ideally, the issue filter (JQL) used by the My Requests view should be configurable. I want to let my customers really see issues "Created by anyone", but I can't do that at this time.

            Can Atlassian please confirm that the "Created by anyone" filter definitely provides search results where the current user is the reporter or a participant? I can't see it documented anywhere. Thanks

            Debbie Ryan added a comment - Can Atlassian please confirm that the "Created by anyone" filter definitely provides search results where the current user is the reporter or a participant? I can't see it documented anywhere. Thanks

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Votes:
              55 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated: