I have a following automation which should trigger an e-mail notification being sent to a reporter if ticket has no attachments, but it doesnt seem to work, as no notification is being sent to a reporter, or others...
The first part works, but the second ("else") doesnt... And it should be working (as if there is no attachment in the issue, it should send an e-mail to the reporter.)
Regarding your automation error, did the issue get assigned to the user triggering or not? If not could you try to reorder your automation to assign before the transition?
regarding the error associated with the manual transition can you share your validation details. I suspect you are requiring an attachment during transition vs. simply requiring the existence of an attachment.
Hi Jack and thanks!
The automation error was resolved by re-ordering.
Regarding the validation - please find attached screenshots. Ive also found a workaround for this by adding a transition screen, but then it would require user to RE-add the attachment again, even if he did so in the initial creation step.
This Validator requires that you update the field during the transition which is made clear in the text of your image. Generally you use Conditions to prevent a transition if a preexisting condition is not met. You can setup as follows…
use the “!=“ operator and leave value field blank.
ive rebuild the automation , and mail-sending works, but now ive got the following error message in the log (please see a screenshot).
Ive also tried to add a validation in the transition displaying a message if there is no attachment, but in that case - even if there IS an attachment - message is displayed and system reverts the status to "TO DO", which shouldnt be the case (Second attachment). Ive reported it on https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-697775
P.S.-sorry for trouble but ive set everything else beside this, and its my third day on JIRA Workflow :)
I see... And yeah, it was giving problems, however - i presume when something is validated and denied, we should be able to inform the user, weather via direct message or an e-mail.
In this case, Jacks method of using the "!=" string - condition during transition works, however user cant see a reason why he can not switch a status.
“Organizations are made of people who create and follow processes which are constantly changing and are in need to be supported and nurtured… this is the spot where I realized I can br...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events