Hey guys -
I'm currently travelling on business and a long time ago we decided to filter out all out of office messages in JEMH, but the issue is that if you are following a pure Jira workflow you get no notification of the fact that someone is out of the office.
As we are using both Scriptrunner and JEMH do you think there is some way to reassign issues that get assigned to someone with an out of office set, but consume the message so it doesn't create thousands of updates in the comment history?
Ideally I'd want to get JEMH to execute a scriptrunner script or maybe do it itself, but populate a field when the assignee has an out of office set.
It's a complicated problem, but I'd imagine it's not unique to us - as many of our support engineers are on the road but peridically on sites where they have no JIRA access I think it's becoming more of an issue.
What do you guys do about it?
This is not a solution using Scriptrunner (not sure if ScriptRunner supports it), but there's an add-on to add comments and reassign issues when someone is out of the office:
Hi Scott, we didn't pick up on this. setting a field value can be done, but managing it is harder, eg we add a user to a multi-user picker field when we receive an OO message, what then? later the user may be 'in office' but still listed out. what impact would this be expected to have to notifications if any?
If you are still looking for an email processing driven outcome, please file a more detailed walkthrough of what you want to have happen in context of a few users doing that, and then becoming 'in office' again.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs