ScriptRunner vs Automation for Jira

[Benjamin Peikes]

So we're at the point where Jira just can't do some of the things we'd like it to do, and are looking at a couple of plugins. Some of the features that we need are related to how issues can be updated on various transitions, others are related to actions that we would like to perform, for example we'd like to be able to:

"Replace User" - Take one account, and replace references to this user in tickets with another user

1) Go through all issues which have old user as reporter and switch it to other account
2) Go through all issues which contain old user in request participant, and add new participant
3) Go through all issues which contain old participant, and remove it
3) Disable old account

We see many more people install ScriptRunner, but we'd like to hear what other people's experience with the two tools are.

[Danyal Iqbal]

Hi

I would definitely suggest script runner. It is the more mature of the two and it will be around longer. It has a steep learning curve, but it is well rewarded in terms of the stuff it can do.

P.S:  "Replace User" is a bad idea. Don't do it.  Old users are not meant to be forgotten or replaced. You need to rework your use case instead of this useless exercise. Both these tools are meant to generate value by reducing overhead and probably too expensive  for 1 time use. The cited example is a poor use case for these tools.... Howeve, if you must replace the users,   I would suggest this tool for bulk changes:

https://marketplace.atlassian.com/apps/1212559/bulk-action-tools?hosting=cloud&tab=overview

 * search for all issues with references to old user

* click bulk action

* select all issues

* make changes to all the selected tickets e.g replace the reporter

[Benjamin Peikes]

Replace user is a requirement because Atlassian does not allow a user to have multiple email addresses. This is what happens to us:

1) A user has email address A, they use it to create support tickets for a year.

2) User changes their outgoing email address, though they still can receive emails at address A. We update old tickets, and they get responses, but now, any of their responses to their old tickets spawn new tickets, because Service Desk sees it as a different user.

3) Since the user has opened new tickets with email address B, there are now 2 Service Desk users, though they are the same person.

We would use the Bulk feature that Jira already has, but it does not support replacing a user in the "Request Participants" field, which can have multiple users in it.

This happens to us on a regular basis. Does not have a way to combine tickets, nor do they have a way to "replace" users, as described.