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,559,471
Community Members
 
Community Events
184
Community Groups

Same team looking after Jira service desk project & agile scrum project board, What is the best way?

Edited

Hey Guys,

Looking for advice from Jira experts.

My dev team is looking after a Jira service desk project and an agile scrum project for the same software development project. 

I am exploring what is the best way to handle this rather than having to look after 2 projects separately. Also, I like to hear how everyone else is looking after support requests while working on sprints to develop features.  

Cheers

1 answer

1 accepted

1 vote
Answer accepted
Aaron Geister
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 11, 2021

In most cases, I would say the dev team should be on agile process and development project and IT support tech should be taking care of the JSM project and forwarding issues to that team. This reduces the dev team being responsible for two projects. 

Now that team field is available with advance road maps with premium access it helps to route issue to teams. 

ITSM can be used for multiple team access. I do believe they shouldn't have to administrate it only work from dev tickets that come in. 

You can also clone issue and automate a process to clone issue to their projects for development bugs or other reasons. 

 

I hope this helps. 

Much appreciated, @Aaron Geister 

The main issue I am facing is since we just released the MVP, many of the support tickets are software-related issues/bugs that need dev involvement.

Like Aaron Geister likes this
Aaron Geister
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 11, 2021

Two ways I have handled this in the past. 

1st. Add dev team to project use a team responsible field with automation to alert that team of issue and allow themselves to add an assigned user from that team. 

 

2nd. Create an automation when a dev issue comes to the ITSM project have it automate the issue to clone the issue into the dev project as a bug or task. Have it carry all information and link the issues together. 

 

I would try one of these two options. 

Like Roshan Milinda likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events