I presume you leave it unassigned at creation time, correct? You'd need a script to run and being in the cloud you don't have access to scripting.
I would say that Service Desk automation might help, but even that won't pick up "person looked at an issue"
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.
Server add-ons are not allowed on Cloud, except for the pre-selected list of ones Atlassian are willing to support there.
You can install Connect add-ons, but the structure for those is quite limiting and there's nothing really resembling a scripting add-on for them.
My mob include Jamie Echlin, the writer of Script Runner (for server), and he's looked at doing it on Cloud. I'm not going to pretend I understand half the limitations, but one example of why SR for JIRA Cloud has not been done is that there's no way for it to do Conditions or Validators on transitions, it can only do post-functions. The Cloud/Connect API simply doesn't expose enough power to allow for much scripting.
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.