I would like to be able to define an automation like this:
Step 2 appears to require some new functionality. We already have a 'for each returned issue' function in 'Branch rule/related issues.' How difficult would it be to adapt this to any iterable list, and introduce an iteration variable that can be referenced in step 4 ('{{watcher}}')?
Or, can someone suggest a way to accomplish the same thing another way? That is to say, users who opt-in to Slack notifications (members of the 'slack-notify' group) get Slack direct messages when an issue they are watching is updated.
I already have this working nicely for when tickets are assigned, the difference being that I only have to deal with one user.
Hi Sean,
Yes, we don't support this yet, but are already tracking this at https://codebarrel.atlassian.net/browse/AUT-81. We've got quite a few higher priority items in our backlog at the moment so it will be a while before we can get to this, but we'll let you know when we get a chance to work on this.
Cheers,
Andreas
Thank you very much Andreas. I'm happy to know it's on the list -- it will make your add-on even more indispensable than it already is!
Cheers,
sean
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.