You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have a Custom Field (Start Date) which is of type Date Picker.
When an automation is fired and the ticket moves into In Progress, I want to set Start Date to the date, based upon the day (not date/time) the ticket was transitioned.
I initially used {{now}}, but that sets everything to UTC -- which isn't always correct. Instead, I want it to the day, relative to the person who initiated the status change.
I realize there's an {{initiator}} and I tried convertToTimeZone(initiator.timeZone). But that didn't work. Any ideas?
Hi Doug, have you looked at the documentation on date functions for automation? date-and-time-functions . While quite powerful I don’t see how you could find the date/time based on initiator location unless you had a custom field that the initiator filled in at the time of transition, e.g. UTC-Offset would be useful.
Hi Jack,
Thanks for the response.
I did read the documentation and tried multiple google searches...
But I didn't see anything useful. Which is why I asked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it. Maybe someone has come up with an idea but again I don’t see an option to detect the users location.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Doug Levitt
Would you please provide your entire edit of Start Date for some context? When I tried these they worked for me:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Thanks for the reply.
So, I created a simple "test rule", which fires when a issue goes to done and sends a message to a "test" Slack Channel.
The slack message is:
The following issue transitioned to Done:
- {{issue.key}}
- Creator *{{creator.displayname}}*
- Creator Time Zone *{{creator.timeZone}}*
- Initiator *{{initiator.displayname}}*
- Initiator Time Zone *{{initiator.timeZone}}*
- Now *{{now.shortDateTime}}*
- Now Creator *{{now.convertToTimeZone(creator.timeZone).shortDateTime}}*
- Now Initiator *{{now.convertToTimeZone(initiator.timeZone).shortDateTime}}*
Bellow is what is written to the Slack Channel
I was the creator and initiator of AEP-723. For some reason, the initiator isn't associated with a timeZone. I could see other attributes of the initiator (e.g. the email address). But not the timeZone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Out of curiosity, I tried to "Log[ging] in as [another] user" (I am an administrator with full capabilities).
When the other user (who I was "impersonating") moved the issue to Done, {{initiator.timeZone}} displayed a valid value (for Initiator's TimeZone) in the Slack Channel.
Now I am curious why this isn't working (for me).
Doug
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Doug, this sounds like you have uncovered a defect to log. ;^)
I am running as a project admin when I run the rule (when this worked), and don't have site admin to confirm your findings. And I did not see this symptom in the Code Barrel or public Jira Cloud backlogs.
__Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.