Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unlock the power of search with the new JQL editor

68 comments

Now clear up the issues with JQL between epic name and epic link. When I search issues based on epic. I want to export those issues with the epic name.

The link is not meaningful at all to everyone.

Like # people like this

Is this feature not available for Free Jira instances? I don't seem to have it in my domain. :( 

Hi Nick and @Darren S_ Eyers that's right we are not extending the JQL grammar in this release. 

@Timothy Bassett thank you for that suggestion, that's a great idea and we do have it in the backlog, we'll see when we could potentially bring it to life.

@Tony Nathan we are planning to land this in Advanced next year.

@Dipak Naokar thank you for flagging that ticket. It's on our long term backlog, we do not have a set timeline for adding that feature yet. 

@Eilif Johansen Yes

@Mark Kassar , you need to rewrite the query in the new JQL editor that is available in the "Issues" tab in your projects. This feature is deployed on all cloud instances

Dan, thank you for the suggestion, we are working on cleaning this up eventually.

@Tanya L Christensen - this feature is available on free instances - please check under "Issues" in your projects :) 

Like Tanya L Christensen likes this

Great improvements!! 👍🏼

Like Yerbol Nisanbayev likes this

@Yerbol Nisanbayev I actually created a very simple (new) JQL literally to query the project for all tasks assigned to one person, still the same issue.

Like Yerbol Nisanbayev likes this

can this feature also be used in the "advanced issue search" for searching for tickets and creating filters? or is it just supposed to be used from within the project issues?

Like Yerbol Nisanbayev likes this
Jack Brickey Community Leader Aug 30, 2021

@Max Wallisch , there is a lot of questions and answers about this very thing within the comments. Basically it is not there today but is intended to be there but not till next year. 

@Yerbol Nisanbayev , I would recommend adding this information into the main post so that future readers will understand this limitation upfront.

Like Yerbol Nisanbayev likes this

@Jack Brickey thx for the info. maybe add that in the article as well. I did not want to go through 3 pages of comments just to see if that info might be in there somewhere.

Like Yerbol Nisanbayev likes this

Thanks @Yerbol Nisanbayev - Thanks.   That's not how I typically search for issues.  I use the Filters at the top of the UI.  Interesting that the feature doesn't work in both places. 

Like Yerbol Nisanbayev likes this

Hey @Mark Kassar , send me a screenshot or a video of what you are trying to do to ynisanbayev(at)atlassian.com and I'll take a look :)

@Jack Brickey and @Max Wallisch DONE

@Tanya L Christensen we are iteratively building it out, soon enough it will be available in both places and we will have filter support in the better issue navigator too. 

This looks great and is nice, but since most of my complex queries are in Sprint Boards or Dashboards I still have the problem of not being able to see  user names for queries. My asking around says that our userbase only uses project queries casually and is mostly using the "Filters" tab for creating queries, it won't be terribly useful and might even confuse some of our more casual Jira users as they see two styles for query creation. I see that I can create the queries in the project page and then copy it to the "Filters" page, but as you stated, it goes back to the terrible user ID string.

I will advertise is to the user base after you get the most important part of search in this new mode. Please hurry.

Like Yerbol Nisanbayev likes this

I guess user names in search/filters are a bad practice. Imagine the person you have on dashboards leaves your company. Information will become irrelevant and you will need to find all places where the person is mentioned (using GUID, not his name) and replace him with someone else. It is a nightmare. 

 

Using groups is more convenient. I have groups for most teams even if team consists of one person. Moreover user can be in several groups. On project level I use roles based permission scheme. This is perfect for sharing project settings in case team stops working on one product and begins working on another. Or we have several teams which make similar projects. I just copy project settings and voila - it is ready for work.

Like # people like this

@Yerbol Nisanbayev I have sent you a video by email.

 

Thanks

Mark

Like Yerbol Nisanbayev likes this

@Sergei Gridnevskii  We do use groups and roles most extensively for our company wide filters that are developed by the admins. However, for the bulk of users, I don't believe that they can see the member list of any of the groups and so they don't use these. Does anyone have a simple way for typical users to see the group membership lists? Additionally, only admins can create groups. I think that we have taught our project managers and project admins to use roles for filters in their specific projects and so the obsolescence of filters for individual names in them is in decent shape. 

Like Yerbol Nisanbayev likes this

@Mark Kassar thank you, responded :) 
@Tom Holden you are right that we need the same functionality in filters in advanced search and we will bring it on board next year - we are currently working on it. We are shipping these changes step by step iteratively to learn from what customers tell us and build the capacity to replace advanced search and filters with this new better experience. 

now can I use "resolvedDate > DueDate"?

@Dyego Mota  , the ability to perform date comparison is not part of the functionality described here. If this is a comparison that you need to do frequently you might consider using automation along with a custom field. The way this would work is that once an issue is resolved it would trigger an automation rule which would then perform the comparison of the two dates and set the custom field accordingly. Then you can use the custom field in your JQL query. 

Like Elizabeth Nixon likes this

so simple but not possible :(

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you