Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-83341

For issue search, ability to seach a certain Asset object type field without an AQL search

XMLWordPrintable

    • 0
    • 2

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

      Currently, in issue search feature, when they search a certain Asset object type field, they should use AQL.

      Now, Atlassian was tried to introduce the new issue search for Jira Cloud.

      For new issue search, it would be useful to add an ability that a certain Asset object type field without an AQL search in basic search.

        1. screenshot-1.png
          screenshot-1.png
          121 kB

            [JRACLOUD-83341] For issue search, ability to seach a certain Asset object type field without an AQL search

            Knut Arne Ristebråten added a comment -

            This issue causes problems for our users.
            Since Assets often are used to categorize e.g systems, the Agents normally will search in asset fields to find issues.
            Usually "superusers" have the knowledge to search with AQL, hence for normal agents will not be able themself to find tickets...

             

            This is a major loss in functionality when migrating to Cloud.

             

            Also - I am surprised for this behaviour, because if you switch to advanced JQL one are actually presented with autocomplete for asset fields with dropdown menu...

            Knut Arne Ristebråten added a comment - This issue causes problems for our users. Since Assets often are used to categorize e.g systems, the Agents normally will search in asset fields to find issues. Usually "superusers" have the knowledge to search with AQL, hence for normal agents will not be able themself to find tickets...   This is a major loss in functionality when migrating to Cloud.   Also - I am surprised for this behaviour, because if you switch to advanced JQL one are actually presented with autocomplete for asset fields with dropdown menu...

            Marc - Devoteam added a comment -

            See also https://jira.atlassian.com/browse/JSDCLOUD-13738

            Marc - Devoteam added a comment - See also https://jira.atlassian.com/browse/JSDCLOUD-13738

            Sachin Dhamale added a comment -

            Any updates on this?

            Sachin Dhamale added a comment - Any updates on this?

            Johan Wolfhagen added a comment -

            Assets fields are very useful when implementing processes, but not giving the non-technical users a simple way to perform searches is really a shame. This feature request is very basic to have in place if you ask me  

            Johan Wolfhagen added a comment - Assets fields are very useful when implementing processes, but not giving the non-technical users a simple way to perform searches is really a shame. This feature request is very basic to have in place if you ask me  

            Noah Dinlemez added a comment -

            My company would love this as they use Basic search a lot. Altough I can see a problem with context, it should be typable (with suggestions) based on just the name. It cán understand this when using Advanced (JQL) search...

            Noah Dinlemez added a comment - My company would love this as they use Basic search a lot. Altough I can see a problem with context, it should be typable (with suggestions) based on just the name. It cán understand this when using Advanced (JQL) search...

              Unassigned Unassigned
              a5d57c498007 Takeshi Muramatsu
              Votes:
              7 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: