nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Service Desk - Moving an Issue based on Keywords

Jarrod Mochnick

Hello,

We have two Service Desk projects. Each handle different requests. I was wondering if it was possible (preferably out of the box) to automatically move an Issue that is created based on the Summary line.

For example, lets say we have two SD projects. One called Hardware, the other called Software. If someone emails our email channel with 'Software support' in the subject, the automation detects 'software', and automatically moves it to the Software project. We only have one email address for our end users to reduce confusion on which service desk they need to contact.

Accepted answers

All comments

Brant Schroeder

There is no default automation to move issues between projects. I would suggest having a single service desk project and moving the issues between queues. This can easily be automated using the automation rules in the service desk.

Jarrod Mochnick

I see what you are saying, but we are already well into production with two separate projects. We have two separate teams entirely with different automation rules, SLAs, and others, hence the need for two projects.

Do you know if it is possible with an add-on?

Thanks!

Brant Schroeder

I don't know if there is a add-on that will do this. We run six teams out of a single service desk and started off with multiple. They have distinct queues, components, SLAs, and workflows. We use email aliases to help filter and automate email requests. We use the portal as our main end point to ensure we get good information from the customer and so they can self service. Combining was not that hard and just took a little training.

Depending on your organizations structure that might not be the way to go but to move issues the agents have to be agents in both projects. So really the visibility is the same.

unknown

How did you achieve automation with separate aliases? I am working toward this myself.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk

automation