You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
A ticket has been raised (VSD-158) and I clicked "reply to customer" from within the ticket. When the customer replies, it creates a new ticket (VSD-159 and VSD-160).
The subject in my first email comment to the customer was "https://voice-global.atlassian.net/browse/VSD-158#icft=VSD-158 New terms and conditions popup" so it should match with the ticket ID, shouldn't it?
Here is the ticket queue:
and here are the comments within the original ticket:
Thanks,
John
The email the customer received had the subject:
hmm... it won't let me post it because it's reading it as code. I'll post a screenshot instead:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's very strange - usually it would just have the Key not a link I think.
Can the user confirm what they did to reply - did they include another email address? Email isn't an exact science for Jira, so even when it looks like you've done everything right it can still throw up an anomaly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've asked them although I imagine that they just clicked reply in Outlook.
It wouldn't be anything to do with the fact that our emails have two different names for the same account? So everyone here (at the university) has person.name@newcastle.ac.uk and person.name@ncl.ac.uk (I don't know why tbh... they both work the same).
Reason I mention is because the initial ticket was raised on the customer's ncl.ac.uk and the replies were from newcastle.ac.uk...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, John! It will see the reporter as two different people.
Also, the @newcastle.ac.uk account would not have access to the @ncl ticket.
The solution to that is to always add the other account as a request participant. Very messy from a notification point of view though.
Regards, Liam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, unfortunately I can't do anything about the two versions of email addresses... As you say, for each ticket I'll have to link them and add request participants... Thanks for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.