nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Log work for user with automation rule

Michelle Gaul

Hey there!

I am using the add-on "Automation for Jira" on Cloud. In my service desk, there are two custom number fields, in which our agents note their travel and "labour time" for this issue. we also have a custom field in which the date of the appointment is typed in.

via an automation rule, the inserted time in the "travel time" and "labour time" field are logged against the issue according to the date of the appointment.

for example:

trigger: field value changes for  "labour time custom field" OR"appointment date custom field"
if "appointment date custom field" != EMPTY AND "labour time custom field" !~ "0"
then log work:
time spent: {{"labour time custom field".value}}m
date started: {{"appointment date".value}}

we do this, because it is quite important to us to differentiate between labour time and travel time.

now the problem is, if the work is logged through the automation rule, the user for "logged by" is "Automation for Jira". we want to change that user to either the initiator of the rule, the assignee or the mentioned user in a custom field of the issue. Is it possible to change the user for whom the work is logged already in the automation rule itself or through another automation?

I am very looking forward to your responses! thanks in advance

Michelle

Accepted answers

John McKiernan1

Hey Michelle,

unfortunately, we aren't able to change the rule actor in Cloud due to API limitations. We are tracking it here: https://codebarrel.atlassian.net/browse/AUT-56

If we can do it, I will pop a notification here once shipped.

Sorry couldn't be of more help with this one!

Cheers,

John

All comments

John McKiernan1

Hey Michelle,

unfortunately, we aren't able to change the rule actor in Cloud due to API limitations. We are tracking it here: https://codebarrel.atlassian.net/browse/AUT-56

If we can do it, I will pop a notification here once shipped.

Sorry couldn't be of more help with this one!

Cheers,

John

Michelle Gaul

Hey John,

that's unfortunate, but thank you for your fast reply!

if I understood the "Backlog" category correctly, it won't be implemented within this year, right?

Do you have any Workaround idea maybe?

we are currently customizing our reports and want to see a list of travel and labour hours per agent. But as of now this is not possible, because all hours are logged for "Automation for Jira" and not the actual Agent.