1) Is there a way to do this without doing a "bulk change"? I have attempted to write automation for this and based on the audit log it states successful, however when I go to check the field within the task it is still empty.
2) Is there a way to transition a specific issue to a different status once a field has been updated?
P.S i have no formal training on writing these so if you could please provide a solution in the simplest way possible lol
thank you all in advance!
To summarize the answer given in the thread - make sure the Edit fields component is copying from the Epic issue or Trigger issue.
Using Copy from current issue literally copies from the same issue you're editing (not the parent/epic) which will return a Success results but not change the value at all.
Hello @Darrian Castillo
When looking at the Audit Log for an Automation Rule you can get more details about what happened when the rule executed by clicking the Show More link. Please click that on the last successful execution of the rule and share what it says with us.
Can you also provide screen images that show the details of each step in your automation rule?
Regarding your second question, yes, it is possible to automate changing an issue status when a field in the issue changes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your quick response. Please see screenshot below of the "show more". This reflects it updated all of these issues, which is exactly the issues that need to be updated.
For example: If the EPIC field "Greenlgiht Date" (which is the date picker format) is updated - I want all issues with the same field "Greenlgiht date" within the EPIC to be updated.
Additionally, here are images of the details for each step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem I see is on your *Edit* step.
When you refer to "from Current Issue" it is referring to the child issue you're currently iterating over, causing this update to make no change.
Click on the *...* in front of Copy Greenlight Date from Current issue and change it to Copy from epic or Copy from trigger issue.
Cheers!
Filipi Lima
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fillipi!!
oh my gosh! thanks so much!! It worked!! if I wanted to do that for other fields would i have to create separate automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm glad to help, Darrian!
You can change multiple fields within the same Edit issue component by clicking on Choose field to set.. and picking up the others.
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.
Hi again!!
Thank you again for assisting me with my first question about updating a field within the EPIC to update the same field in the related tasks! That has been a success.
I have figured out my second question - but want to add one more additional condition to do a second transition to "done." Please review the screenshot below - this current automation is successful, however, I want to see if after the scheduled SIV date has been reached. For ex: SIV date is 04/12/2021 on 04/13/2021 transition issue to "Done".
Is that possible to do?
The workflow is as follows "Not started" - "In Progress" - "Scheduled" - "Done"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To have an issue automatically transition on a date based on how that date compares to a date stored in a field in the issue you will need to create an automation rule that runs on a schedule (i.e. daily), look for the issues where SIV Date is in the past, and then transition the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Thank you so much for the breakdown! This has also been a success! Is
I appreciate you, @Filipi Lima , and the Atlassian community! Everyone is so willing to offer their support and provide solutions! You are all amazing!!
I am sure I will be back soon with more questions! lol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome @Darrian Castillo
If your problem has been solved and your questions answered, can you mark the responses as Answer Accepted? That helps other users searching the community find the posts that provide useful answers.
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.
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.