Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira Automation - Vendor Risk Assessment - Inserts date 365 days out + Copy Vendor Name

Austin Songer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 05, 2023

I have Jira service desk for performing vendor risk assessments. I want to create an automation that when a ticket is closed for a vendor it automatically creates a new ticket and it populates the the "due date" 365 days in the future and this is a a way of ensuring that every vendor risk assessment is done yearly for each vendor.


I keep trying to make it work, but the vendor name or the date is not populating into the new ticket. Here is every step.



Screenshot 2023-11-05 at 12.47.27 PM.pngScreenshot 2023-11-05 at 12.47.34 PM.pngScreenshot 2023-11-05 at 12.47.41 PM.png



1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 05, 2023

Hi @Austin Songer -- Welcome to the Atlassian Community!

Are you trying to edit / set the fields Review Date and Vendor in the newly created issue or the trigger issue.  As written, the rule will try to edit the trigger issue.

If you want those set in the newly created issue, you have a couple of options:

  1. set the fields at the same time the issue is created
  2. after creating the issue, branch to most-recently-created-issue and then perform the edits; again, these could both be done in one action

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events