JQL for worklogged last week sorted by work logger.

[Mukund Iyer Rajamony]

Hi,

I have a JQL 
project = "abc" and worklogData >= startOfWeek(-1)

which works reasonably well. I can see a list of issues for which work has been logged last week so far so good.

However, it might seem very disquieting to realise that I cannot sort this information using JQL by who actually logged that piece of work.

While I can see in a specific issue in the work log tab who actually logged it, I can't seem to query without necessarily buying yet another plugin in the market.

Can JIRA somehow provide this query mechanism by default? If not, I really really would expect JIRA to bundle this capability OOTB.

I am using v7.13.0

[Mukund Iyer Rajamony · Accepted solution]

JIRA should implement an OOTB solution at the earliest.

[Mario Carabelli]

Hi @Mukund Iyer Rajamony

the author of the worklog is saved to and can  be included in a jql statement with worklogAuthor = currentUser() (or an actual username). For more information on the field you can look here:

https://confluence.atlassian.com/jiracoreserver073/advanced-searching-fields-reference-861257219.html#Advancedsearching-fieldsreference-WorkLogAuthorworklogAuthorWorklogauthor

With kind regards,
Mario Carabelli

[Mukund Iyer Rajamony]

Hi @Mario Carabelli ,

Your solution does not fully satisfy my requirement. While I can query for items by a specific wla or a set of wlas, the project query is sufficient for me to get all the time logged.

The result of the query is a linewise view of issues. What I want is to be able to see the wla as one of the columns of the result. I don't mind seeing the same issue repeated more than once, but the main column of interest is the wla.

[Mario Carabelli]

Hi @Mukund Iyer Rajamony

As I understand now (after your reply) you want to sort your issue after the worklogAuthor which doesn't work because it isn't an hierarchical field.

I don't see a possibility to realize this in standard Jira.

I think it is intentional that it isn't included in standard Jira. Atlassian focusses on team work and not on the statistics of singular individuals (because this creates an environment of competition and not of working together as a team).

As configurable Jira is, it still has some assumptions baked into it which fit more to agile software teams then classical hierarchical business structures. I think this is the main reason why some features you consider to be really really important aren't important to Atlassian at all and need an extra App to realize.

But that's just my point of view and maybe there is a technical answer to your original question which I just don't know.

I hope you find a solution/workaround for your problem anyway.

With kind regards,
Mario