Create new JS project linked to existing JSM project

[Scott Bernoth]

We currently has a 1 Service project running in JSM and am now trying to create new Jira Software JS projects.

When we go to https://amm*****.atlassian.net/secure/BrowseProjects.jspa?selectedProjectType=software

https://amm*****.atlassian.net/jira/projects?selectedProjectType=software

create project > https://amm*****.atlassian.net/jira/projects?selectedProjectType=software > the page defaults to the service management project template page

choose Software development > Scrum Template > Use template > Company managed project

On the Add project details page:

If we choose "Share settings with an existing project" and then link the JSM project the new project becomes a Service Management JSM project not a JS.

If we choose to create a project without choosing share settings the resulting new project is a company managed software project. 

What is the best choice to set up a JS project that the JSM project can feed issues to?

[Jack Brickey · Accepted solution]

I agree with Fabian, you should not try to use a JSM project as a template for a JSW project.

Regarding your last sentence about feeding issues between your JSM and JSW project what exactly do you mean? If the idea is that you receive JSM issues that then require software development in one of your JSW projects then simply create a linked issue between your JSM issue and your JSW project. 

[Scott Bernoth]

Thankyou, I will look into linked issues.

[Fabian Lim · Accepted solution]

Hi @Scott Bernoth

My recommendation would be to not to share the configurations.  The js project should have different issuetypes and workflows and you can feed issues to it by using automation or linking issues manually.

The jsm is used for gathering requests/incidents and js tickets will be linked to those requests to complete the tasks.  There are a lot of videos available online that showcase how they work together with automation examples.

Keep in mind that having too many jsm projects with different members consume a lot of agent licenses while js projects are normal user licenses.

I hope this helps.

[Scott Bernoth]

Thankyou