nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Roshan Milinda

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

Accepted answers

A A Ron Geister _Trundl_

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.

All comments

A A Ron Geister _Trundl_

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.

Roshan Milinda

Much appreciated, @A A Ron Geister _Trundl_

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.

A A Ron Geister _Trundl_

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk

atlassian-support

scrum

jira-align