Automation on Issue moved

[pschwarzde]

Is there any way to automate something if a issue is moved? In this case: If an issue is moved from Project A to Project B and no request type is set, a default should be set.

[Earl McCutcheon]

Hello @pschwarzde ,

This is currently an expected behavior at this time and we have a feature request open to improve the behavior of this field to allow ti to be required when moving an issue or marking it as required:

• https://jira.atlassian.com/browse/JSDSERVER-6110

I took a look at our third-party apps Marketplace as well to see if I could locate any app that could help with the Move operation, but haven't found any specifically for this purpose.

I recomend adding a vote to the request to show your interest in this feature being added, as covered in the "Implementation of New Features Policy"  to help influence a priority bump.

Then as a workaround I would suggest creating a saved filter to identify service desk requests that are missing a request type that either gets added to a dashboard gadget or monitored by a project lead to make sure the type is being added to the issues regularly.

You could use a JQL like the following to find all the issues in the service desk projects that are missing a request type:

project in (ABC,EXE,ASDF) AND request-channel-type is EMPTY 

Then either bulk update the issues adding a generic request type or review the requests for individual association if additional action is needed for each request due to multiple options avaliable.

Regards,
Earl

[pschwarzde]

Hi Earl,

thank you, I have voted for this feature. We'll implement a workaround in the meantime like you described.

Thanks,
Patrick

[Earl McCutcheon]

HI @pschwarzde ,

Thanks for the update, and I was doing a bit of additional digging on this as well to see if I could find another workaround for better automation, but the big issue with this is that the Customer Request Type Service desk field type currently does not provide an API for setting this system level field, and any Add-on app would be using the API to do this action.

I was thinking that you might be able to use either ScriptrRnner or PowerScripts  for Jira to do some automation on this action.  As i did find examples like the following noting options to set the request type via a post function:

• https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Script-Runner-set-Field-quot-Customer-Request-type-quot/qaq-p/44063

However  I was again not able to find any examples or confirmation on this in their documentation, or other posts in regards to setting the value during a Move action.  It may still be possible and if you did want to look into automation this using a third party app I would recomend reaching out to to the vendors noted above to see if they are aware of a possible solution for you using a single tool.

But noting the possibility of setting the request type using the post function you could possibly look into using a combination of Automation for Jira and the ScriptRunner option mentioned above to do a On Move action that will transition the destination issue in automation through a looping transition (open to open) for Jira like the following screenshot where scriptRunner would be setting the value in the post function after the automation is triggered as a secondary scripted action triggered by the first:

Regards,
Earl