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; } } }

Software lifecycle - on which Jira instance should I add?

Vanessa Becker_vh489c

Hi Admins!

I have a query with regards to a software lifecycle and on which Jira instance i should add the workflow - the steps taken at Product and Design phase - will it be best suited in Jira Software or in Jira Service Desk? Please could you provide me with your inputs as I am not sure where to build in this workflow... Refer to pic. There will be automation setup between Jira Service Management and Jira Software whereby tickets assigned to a specific status in Service Desk will be created on Jira Software.

My investigations all point to Jira Software - that the workflow for the Product and Design phase workflow must be added in there.

Does anyone else have a similar setup and what Jira instance do you use for the Product and Design phase?

Thank you!

Product and Design.jpg

Comments

Jack Brickey

Hi Vanessa,

My thoughts are to add this into the Jira software product. Anything to do with the product design is associated with software not a service management project. I expect you’ve got automation tying your JSM and JSW projects together such that certain updates in the JSW project will reflect in the JSM project.

JG Meillaud _

Hi Vanessa,

Make it a Jira Software project.

In most internal use cases better stay away from Jira Service Management.

Cheers,
JG

Rich Wolverton

I love your phrasing of the question and the diagram. We think of JSM as a front door. It is an easy way to get communications from a broad audience and then either answer the question directly or funnel the work to the appropriate team and resources while preserving communication back to the initiator. I agree that most 'work' is tracked in Jira Software and now potentially in Jira Work projects.

Maybe you should think of Design as a Jira Work project and Development as a Jira Software project.

Keith Jones_q61emj

We use Jira in this way - for example, enhancement requests are received in the Jira Service Management (JSM). Once it's reviewed and determined to be a true enhancement request, a workflow step will create an issue in Jira Software with the relevant information populated.

There are several reasons for us to do this:
1. We use vastly different workflows for the 2 different projects and we like to keep the number of issue types to a minimum in each project.
2. We have some developers that work only in Jira Software - same thing for JSM, some are agents in that project only.
3. In Jira Software, the "reporter" is actually the BA, so communications are internal only. We use JSM for our communication to the actual customer.

Hope that helps. Looking at this, I'd be hard pressed to make a case for keeping both in the same project.

Welcome!

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