Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Collaborating between 2 service project

Hey Guys,

I have a a team using a service project, and sometime they would need to send the current issue/ticket to another team in a different service project. So naturally the would move it across to the project, than when the team that receive the ticket would move it back to them when they are ready. 

They are using this function to maintain all the comments that went rough that current issue/ticket.

I was wondering if there is any other way to simplify things for the agents while keeping track on the issues.

I have suggested for example to create a linked ticket but they would rather keep everything in a single ticket.

The scenario is this:

They receive a ticket --> they would need to ask something to the other team so they move it to the different project --> when the other team has completed the request they would move it back to the to the original project.

Cheers Aaron



1 answer

1 accepted

0 votes
Answer accepted

Hello Aaron.

What I would personally do in this case is to create a custom field of type "User Picker (multiple users)" and add it to my request types.

You can then adjust both the permission scheme and issue security level for the specific projects so that you grant the required permissions to the users added in this field.

Once you do this, agents can simply add other agents in that field and grant them access to the specific ticket without the need of moving or linking tickets. 

You can even add users in this field via automation if that would be required. 

Information about permissions and sec level:

Hope this helps.

Kind regards,


Hi @Andreas Alexandrou 

Thank you for this suggestion I just would need both teams to agree on this, I was also wondering if perhaps creating a filter where it pick both projects issues and display them as one via a saved filter. I believe this might help.

Cheers Aaron

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events