Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Multiple teams (queues) and access control

Hi Team,

I was reading the below publication from Atlassian:

Jira Service Management: Projects vs Queues | Evaluator Resources | Atlassian Documentation

My concern is:

I am having different teams working in "Service Desk" project. Some teams are external service provides act as 2nd or 3rd level support. In that case, an incident can come from 1st level support (internal) and escalate to 2nd level support (external)

So, is it possible easily flow the same incident from 1st level to 2nd level in an environment where two teams are in two projects?

Having different projects is the recommendation in the publication above. But I may have practical problems as above when I am doing so. I don't think reporting won't be an issue though

Thanks,

Sujeeva

2 answers

1 accepted

1 vote
Answer accepted
Dirk Ronsmans Community Leader Apr 20, 2021

Hi @Sujeeva Tissaarachchi and welcome to the community!

For me this would depend whether those 1st and 2nd line teams are working on the same project. From your explanation it seems they are but just one is more expert in a domain than another.

Having multiple projects could work but i think you would have to then escalate the ticket to the other project by creating either 

  • a linked ticket 
  • moving the ticket (which I would not recommend as it breaks the flow)

There for, I would suggest staying in a single project. By adding maybe a "Team" field which could be a group picker, you can escalate the ticket to that "expert" team and have a queue where a dynamic JQL can filter out the tickets just for them.

If you have the use case where they are only allowed to see the tickets assigned to them, I'd suggest also looking in to issue level security 

So for me (my personal opinion), if they work on the same issues with the same flow but just passing on to another team with more knowledge,I would stick to a single project.

If we're talking a support team (1st line) and a developer team (2nd/3rd line) which have completely different flows well then you could go multiple projects with different issue types and linked issues.

0 votes

@Sujeeva Tissaarachchi -

I agreed with @Dirk Ronsmans answer.  In our envs, we have different DEV-OPS teams (serving as Tier 2+ support) after the initial request is submitted to JSM.  Using JMWE add-on, we utilize JSM custom WF to auto create/auto links JSM issues with different DEV-OPS teams' projects.  We also utilize the JSM out of the box automation, so when DEV-OPS team's projects "linked issues" is closed, then it will trigger the JSM issue closure automatically.

Again, this is because our business needs that we implemented the above solution.  If your needs are different, you should look into further on what Dirk recommended - one project route solution to keep everything simple.

In case you want to take a look at the JMWE add-on, here is the URL from MarketPlace - https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions-jmwe?hosting=cloud&tab=overview

Welcome to the community...

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

856 views 30 33
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