Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to make sure a reporter is notified when raising on behalf of?

When a reporter is changed the reporter doesn't get notifications.

Example of how this works for us.

Someone emails IT, instead of our tech support email. 

The IT person creates a ticket, and changes the "Raise on behalf of" to the person who did the naughty and didn't raise the ticket the correct way.

 

Now the problem is, whenever we comment on that ticket, no email gets sent to the Reporter. I've double-checked and nothing is in spam.

Now, if the reporter emails directly to the tech support, everything goes as expected. They get notified of comments or resolutions, and they can reply back. BUT ONLY if they send the ticket in.

Any help or insight would be greatly appreciated!

1 answer

0 votes
Jack Community Leader Jul 14, 2021

Please verify that the customer request type is actually set. There are two things that need to be set correctly when raising the request on behalf of a customer: the reporter and the customer request type

Wow  seriously! 

Why would that matter for notifications? I just want it to email the reporter back.

The customer request type is set the same regardless of us they emailed it to JIRA/tech support of directly to an IT employee. 

Jack Community Leader Jul 14, 2021

Did that solve your issue? Or is the problem persisting?

Jack Community Leader Jul 14, 2021

Let me rewind here a bit. Who created the issue in the project initially and how did they do that? From what I read initially it seems that the IT agent created the ticket for the customer. Then the question is did they use the create button at the top or did they use the raise a request link on the side bar? If they use the create button it doesn’t go through the form that the customer normally would via the portal as such what is often missed when setting up the request is actually setting the customer request type. Given that issues within all JSM projects deal with customer request type not issue type it is important that that it is correctly set. Otherwise if a customer goes to their portal and looks for the issues they raised the issue will not show up if the customer request type is not set. Note if a customer sends in an email to the JSM project then the customer request type is automatically set based on how the email channel is configured.

I see.

 

How the ticket is usually created is the agent will use the outlook integration. 

Screenshot_4.jpg

The Reporter is then set to whoever is reporting the issue. The Issue Type is set the same as when someone is emailing the tech support email. 

The other thing is, when something is resolved, the setting is to Reporter(customer) and Customers involved.

Screenshot_5.jpgWhich, in my mind, shouldn't matter what the Issue Type is. 

I'll poke around the settings to see if I missed something.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Atlympic Event: Jira Service Managemnt

Hello Community!  Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...

226 views 1 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you