can a team have both service items and non-service (planned) work in a service project?

[Darren]

Jira Software/Core Data Center 9, Jira Service Management 5

Does anyone here use a single Jira 'service' Project that contain both 'service' requests captured via the Jira Service Management servicedesk portal, and the team's own internal 'planned' work items such as upgrades and other technical changes?

Currently we have teams that use two Jira Projects - one 'service' and one 'software' - and then work off a single Board (Filter contains "project in (A, B)")

I'm wondering if these could (or even should) be combined and everything could go into the 'service' project, or if that's going to cause problems.

[Marco Brundel · Accepted solution]

Hi @Darren ,

Combining both service requests captured via Jira Service Management and internal work items (tasks or bugs for example) within a single Jira project is certainly possible.

Please note, to use a kanban or scrum board, you need Jira Software on your environment.

Regards, Marco

[Darren]

Thanks @Marco Brundel 

Yeah, we have Jira Software :)

I could think of only 1 reason why they might want to keep the 'software' project when they've created an adjacent 'service' project: because of all the existing work that's currently in their 'software' project.

However, with a bit of alignment, I guess we could move the issues from the 'software' project into the 'service' project

Having said that: knowing the team, they're likely push back and request they keep them separate because of familiarity or something (that part of the conversation hasn't unfolded yet)

If they do push back and requesting keeping their 'software' project, any compelling reasons to guide them to moving the 'software' issues into the 'service' project?  Or it doesn't really matter and either solution works just as well as the other?