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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,633
Community Members
 
Community Events
176
Community Groups

Ticket creation

Is there a way of avoiding duplication of tickets in the service desk functionality and if so. Is there functionality to merge tickets instead of linking them?

Can you limit or block information provided via email which goes into the ticket via the service desk ie avoiding an email signature been included into the ticket.

Can you have multiple assignees & reporters? As well can you add external users without registering the user(s) ie to help resolve an issue.

2 answers

0 votes
Daniel Eads Atlassian Team Jul 17, 2020

Hi Andy,

To add some more context:

Can you limit or block information provided via email which goes into the ticket via the service desk ie avoiding an email signature been included into the ticket.

Jira Service Desk Cloud current doesn't have a way to trim signatures from emails. This is a frequent ask however and you can take a look at the feature request on our public Jira instance here: JSDCLOUD-5878 

 

Can you have multiple assignees & reporters? As well can you add external users without registering the user(s) ie to help resolve an issue.

Jira purposely only allows a single user to be the reporter or assignee on issues.

In Service Desk, you can use add multiple Request Participants who have access to see the issue on the customer portal and receive notifications about issue updates. You can configure your Service Desk to allow people to sign up as customers when creating issues.

On the backend of things, you would need to license additional users if you want to have more people working on them. It's possible to configure permissions so that issues in the Jira (not Jira Service Desk portal) interface are publicly visible. However, someone would need to have an account in order to make changes to issues or add comments.

Cheers,
Daniel

0 votes

Hi @Andy Nichols ,

Welcome to the Atlassian Community!

Regarding your question about merging tickets: That's possible with our cloud app Merge Agent for Jira.

If you have questions or feedback about our app, don't hestiate to get in touch with our support team.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events