Hello. I have created a custom field that gets filled when a ticket is closed. Now, I want to know who has filled that particular custom field with certain value I am looking for BUT only if 4 different people have logged time in that particular ticket, if those 4 people have not logged time in that ticket then I am not interested.
I have tried something like this:
created >= startOfYear() AND "Forma de Resolución del Ticket" = "Resuelto directo por Consultor" AND status in (RESUELTO, CERRADO, CANCELADO) and worklogAuthor in (bmontes, sylvana, lsocorro, mlena)
However, this doesn't bring me any results and I know it's not correct.
Any ideas?
Hi Helder,
the operator "IN" works like parenthesis around multiple OR operators, so you're searching:
worklogAuthor = bmontes OR worklogAuthor = sylvana OR....
I guess you understand what I'm saying. What you need is an AND.
But what I learned from trying is that searching for:
worklogAuthor = bmontes AND worklogAuthor = sylvana AND....
It doesn't work at all. Which is sad. So you're right that your expression wasn't correct but what I've figured to be a possible solution doesn't work. Let me think about it a bit more.. :D
Best, Max
Max, first of all thanks for your interest.
The expression "IN" works indeed instead of using the OR with each of the persons, which is the desired, meaning that I would like to get the list where the workAuthor is bmontes OR workAuthor is sylvana OR...... If I use the AND it wouldn't ever work as expected because I would be saying that I want to know an issue where ALL these 4 peoples worked on, I just want to cross 1 of these person with an specific value of my "Forma de resolución del ticket" custom field.
In any case, I even tested using only 1 unique user like this:
"Forma de Resolución del Ticket" = "Resuelto directo por Consultor" AND worklogAuthor = bmontes
And I know there are tickets which have those 2 conditions indeed.
So any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh sorry, so I just got your initial post wrong then and you are totally fine with the IN. That's something!
What kind of custom field is "Forma de Resolución del Ticket"? Does your initial query work without that specific bit?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The "Forma de Resolución del Ticket" is just a dropdown with 4 different possible values and has a default value which is actually "Resuelto directo por Consultor".
If I run the following:
"Forma de Resolución del Ticket" = "Resuelto directo por Consultor"
I actually get the list of tickets that have that value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe you and that's weird. From my perspective, there's nothing special here and similar searches return the expected results in my instance. I'm not sure what we're missing here and why your query breaks or returns zero results when you combine everything. So the whole query doesn't return any results as soon as you add the worklogAuthor to the rest? Or combine the worklogAuthor with the custom field? Could you play around with it a bit?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, I played around a lot. It seems to return 0 result when I use the workAuthor. I am not sure I understand correctly what the workAuthor does, maybe I understood wrong, but I was under the impression that workAuthor was intended to filter anything where a specific user would have logged hours (and basically is a filter of the actual username as author of logged hours)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's the correct explanation you can find in the Advanced Search JQL documentation
Search for issues a particular user has logged work against. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have "Time Tracking" permissions, unless you are searching for issues that you've logged work against.
What makes me wonder is that the field worklogAuthor is only mentioned in the server documentation and not in the one for Jira Cloud. But it will be suggested (as are worklogComment and worklogDate, not documented for Jira Cloud too) in the issue navigator. It feels odd and unless you want to spend more time trying to understand why it doesn't work for you but for me, maybe open a ticket with the Atlassian support to have them take a look. 🤷🏼♂️
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I already did a couple of hour ago (opened a ticket) to Atlassian.
In regards of the permission, I am admin so I should have enough permissions, however, I even did a test with my own user (using workAuthor = currentUser()) and it gave me 0, so something must be wrong here....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please keep us posted about your progress and maybe doublecheck your permissions. But if you're able to log work it should return the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After opening a ticket with Atlassian it seems the culript was Tempo, which for some reason breaks the "workAuthor" field usage. They also offered an alternative solution at least to what my goal was, so here it is in case it turns useful for someone else:
Paulo Junior commented: Hi Helder, Thanks for contacting the Atlassian Support. This is a known issue that happens when Tempo is the default time tracking tool. What happens is that the Tempo Timesheets plugin updates Jira’s time spent field on the issue, as many Reports, functionalities and more are relying on this field. However, when Tempo updates the JIRA's time spent field without disclosing any specific information like the worklog author and description. When using JQL, you are retrieving information directly from JIRA. As the worklog author information is not available in JIRA, the JQL for worklogAuthor returns empty. As a workaround, you can create a filter, leaving out the worklogAuthor parameter:
created >= startOfYear() AND "Forma de Resolución del Ticket" = "Resuelto directo por Consultor" AND status in (RESUELTO, CERRADO, CANCELADO)
save the filter and use it in the Tempo Reports view. You can then filter the Report by this JQL filter and the user (worklogAuthor). Please take also a look at https://tempo-io.atlassian.net/wiki/spaces/THC/pages/190119937/Creating+and+Accessing+Saved+Reports+-+Tempo+Cloud for more information. I hope this helps you out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.