User can't run report - worklogAuthor error
Hi,
We want team coordinators to be able to run Jiratimesheet reports but we are getting this error messsage "Le champ 'worklogDate' n'existe pas. Le champ 'worklogAuthor' n'existe pas."
As an Administrator I can run the report, it's the coordinators that I can't figure out how to allow.
I also tried this query "worklogAuthor = currentuser()" in the Issues and the user also gets an error.
I've configured TimeSheets to have access to every group
Comments (18)
-
Account Deleted -
Hi Michel,
Thank you for rising the issue.
However it's not clear for me too, how these JQL functions disappear or not working for some users. May be there is something with permissions, but there is no special permission needed for these functions.
Could you please also rise a ticket with Atlassian Support here https://support.atlassian.com, may be also contrasting it with JST-163246. I may recommend not to mention timesheet add-on to avoid confusion. These JQL functions are JIRA built-in, and must be available for all. Add-on just uses them.
Thank you.
-
Account Deleted -
Hi Michel,
Great! Just note, I can't see those tickets, so if you get it solved, please let me know.
Thank you.
-
Account Deleted Andriy,
I got some feedback from Atlassian. Here is what I got.
"By running the JQL I see that the integration between JIRA + Tempo is working fine this time. But by switching to Marie Jacob user to run the JQL again, I found a kind of permission error related (as you might checking using this validator). Since I can't troubleshoot it further, I kindly suggest you to contact Tempo Support in a way to get this issue resolved. "
-
Account Deleted The validator being ".../secure/tempoValidateDate.jspa"
-
That's interesting. As you might know Tempo is different plugin, so could you please contact them: https://tempo.zendesk.com/hc/en-us
I have not managed to find anything relevant though. Basing on this: https://answers.atlassian.com/questions/93415/log-work-for-another-issue-7-3, looks like there is some permission configuration in tempo.
Could you please ask Atlassian Support to add Tempo people to your ticket, so that they could help?
Thank you.
-
Account Deleted -
Thanks! Note, I don't have access to it either, but I still will be interested if you get any news!
-
Account Deleted Tempo found this:
Checking on JIRA logs, here's what I found: 2015-11-06 13:29:34.616206500 2015-11-06 13:29:34,616 ajp-nio-127.0.0.104-8009-exec-130 ERROR marie.jacob 809x417105x4 m1r95x 104.192.142.137,165.254.226.145 /rest/tempo-rest/2.0/team/5 [c.t.service.roles.TempoRoleServiceImpl] Could not find project role for role id: 10300
-
Hm. Also I'm curious why/how Tempo can hide JQL built-in functions.
-
Account Deleted Andriy,
Here's something interesting, maybe this will give you a hint on what's going on behind the scenes. There are 2 gadgets developed under your name. Time Sheet and Time Report. Just to let you know that Time Sheet works perfectly well but Time Reports sends out the WorkLogDate error.
-
Hi Michlel,
Right, these are my two plugins, but they use different technologies. Timesheet Reports and Gadgets does not use worklogDate JQL function.
From my point of view there is some problem with Tempo plugin, so that worklogDate JQL function is not available because of it.
-
Hi Michel,
Have you got any response from Temp team about "Could not find project role for role id: 10300" problem, that most likely causes worklogDate and worklogAuthor JQL function disappear?
Thank you.
-
I've created https://ecosystem.atlassian.net/browse/ACJIRA-722 again.
-
- changed component to Time Reports
-
Hi @michelcote1,
Could you please help Tempo developer to reproduce the problem in TT-3000?
Note, I have seen that your instance is still experiencing the problem sometimes, may be for one specific user, so may be you can clarify what is that special about the user (marie.jacob possibly), like some role/permission settings.
Thank you.
-
- changed status to closed
- Log in to comment
Just to let you know, this request is different than the one below since Admins CAN run the report. In this case it's the user that can't run the report.
https://bitbucket.org/azhdanov/jiratimesheet/issues/694/report-not-running-anymore