I need to get a pure clarifications about two fields called worklogAuthor and Assignee. When I'm using JQL, sometimes, I am unable to get expected results using worklogAuthor. but assignee does.
Hello @Asanka Garusinghe
Assignee means the person to whom the issue is assigned and workLogAuthor is the person to logs works on the issue i.e. Time spent on the issue can be logged by 10 people and each of them will be workLogAuthor but assignee can only be 1 person for each issue in jira.
thanks for the reply @Tarun Sapra
what could be the main reason of getting two different results when I'm using advance searching for worklogs with below mentioned json parameters.
This one returns data.
{
"jql":"assignee = chinthaka AND worklogDate >= '2019-04-01' AND worklogDate <= '2019-04-30'"
}
But this doesn't return anything.
{
"jql":"worklogAuthor = chinthaka AND worklogDate >= '2019-04-01' AND worklogDate <= '2019-04-30'"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both are different queries
First one gets the issues which have assignee "chinthaka" and work was logged on the issues b/w the specified dates.
Second one tries to get issues which had work logged b/w the mentioned dates and the also on the issues the user "chinthaka" has logged work but not necessarily between the worklogDates mentioned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks. @Tarun Sapra
but however, we have an issue of getting worklogs for that corresponded user even he has logged his times in jira between aforementioned date period.
once I'm consuming /api/2/issue/{issuekey}/worklog with specific issuekey, we have the response something like this for author.
"author": {
"name": "addon_is.origo.jira.tempo-plugin",
"key": "addon_is.origo.jira.tempo-plugin", .... }
is there something going wrong?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using tempo 9.x and I don't have this issue, I see the username in the author name and not the ""addon_is.origo.jira.tempo-plugin"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asanka Garusinghe and @Tarun Sapra
This is a Cloud specific problem and does not happen on the Server version.
When worklogs on Cloud are created in Tempo, the information is synced to the JIRA database. JIRA displays worklogs in several places and this might break the permission settings in Tempo. Therefore the worklogAuthor and worklog description information is not synced to JIRA. All worklogs show as having been made by Tempo Timesheets (addon_is.origo.jira.tempo-plugin is the Tempo Timesheets system user).
To retrieve information about the worklog owner, please use the Tempo REST API. Please take a look at https://tempo-io.github.io/tempo-api-docs/ for more information.
Regards,
Susanne Götz
Tempo team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank You @Susanne Götz _Tempo_
Currently, I'm accessing JIRA Rest API with generated basic authentication header with email and JIRA api token. (Referred this: - https://confluence.atlassian.com/cloud/api-tokens-938839638.html)
are we able to use same approach for Tempo REST API?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asanka Garusinghe ,
Tempo REST calls require a OAuth 2.0 token. When using the Tempo REST API as an individual user, this token can be generated in Tempo, Settings, API Integration. Authentication needs to be done via bearer token, f.x:
curl -v -H "Authorization: Bearer ${token}" "https://api.tempo.io/core/3/worklogs
When using the Tempo Servlet ( which is designed for machine to machine communication), the Tempo Access token is required. This token is listed in Tempo, Settings, External Systems Token. This token needs to be added to the URL.
Regards,
Susanne
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Susanne Götz _Tempo_ ,
We are using Tempo Timesheets to store the Worklogs logged in JIRA.
When importing Worklogs with Power BI Connector, the WorklogAuthor is correct for issues in JSM project and issues in a project with XRay, but for issues in a JSW Project the Worklog Author is always "Tempo Timesheet". Why is that difference?
Thank you in advance.
Regards,
Cristina Araújo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cristina Maria Rodrigues Garcia Araújo ,
You can see the differences in this KB for Jira worklogs and Tempo worklogs.
Hope this helps.
Best regards,
Susan Wu
Tempo Product Expert
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.