Comments
-
Thank you, @Janice .
-
Ok, let’s go :-)
-
Welcome and enjoy, @Jeff Tillett !
-
Thank you for all the work, I really appreciate it!
-
Hi @Nils Medina , also, you are missing word issue in the smart value, it should be probably: {{issue.Time in Merged/Built.diff(now).hours}}
-
Hi @Nils Medina , please try to add the Log action to find out value of your smart value {{Time in Merged/Built.diff(now).hours}} https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/
-
Thanks @ALL IT ONE . In that case I believe you have two options: * As a reporter use one of your users with JSM licence and create custom fields to store information about your customers (for example one for the customer name and one for the customer e-mail). * Create customer account in JSM project (see here) and use the…
-
@ALL IT ONE I still don’t understand much your usecase. To which type of Jira project are you trying to create an issue? Is it Jira Software or Jira Service Management? You are saying your clients are creating an issue. Why are you doing this using REST API? Are these clients users of your Jira and have product license or…
-
Exactly @Jamie MacDonald !
-
Awesome updates, thank you.
-
Hi @ALL IT ONE , in cloud the user needs to have Atlassian account created. Each account has unique id (=accountId), which you need to provide. Please see here - in the sample body data there's: "reporter": { "id": "5b10a2844c20165700ede21g" } This id means accountId.
-
Hi @ALL IT ONE , welcome to the Atlassian community! Please, which API endpoint are you using? Are you trying to create a request on behalf of your customer? If yes, please see here In general you need to provide accountId of your user (not name and user).
-
Yes, it looks like it is working again! THANK YOU!
-
I had to google Wordle, I’ve heard of it many times, but didn’t know what it is exactly… :-)
-
That’s nice!
-
Oh wow, these are interesting!
-
Exactly, killer sudoku is my favorite. Thanks for sharing so much detail, I really enjoyed reading your post.
-
Nice one @Andy Gladstone !
-
Hi @Gal Fatal , congratulations! There are two links to MJSP certification in your article - the first one probably should be replaced with MJCP certification.
-
Hi @Andy Gladstone , I can prepare something for tomorrow, if it helps…
-
Hi @ddahlke , if my answer helped you, would you please accept it, so it can help others in the future? Thank you.
-
Hi @anna.kovacsova , welcome to the Atlassian community! It seems to me your rule is correct... What about to use Edit issue action instead of Assign issue, add field Assignee and copy Assignee from Trigger issue?
-
Hi @ddahlke , please try to add: AND (component not in (automation) OR component is EMPTY)
-
Ok, it looks like the date is not available, only other params. I’ve searched more on this topic and it is complicated. The easiest solution probably would be to create a new custom field and store the datetime there each time the issue is transitioned using automation (and then get the value from there). Here are some…
-
Hi @Alex , maybe you can try to get it using {{changelog.status}}, see here for more info: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
-
Great news @Janice !
-
Kudos are very addictive :-)
-
Lol, great story!
-
Nice! Thank you! Very useful.
-
Great job!