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

Issue with moving Organizations

Vanessa Becker_vh489c

Hi Admins!

I have about 100 tickets with their associated Organizations that i need to move from Jira Service Management to Jira Software Development but my Organizations is not moving (the organization is not showing / picking up on my software board after I have moved it. See attached error (this is on my Jira Software board)

I also see that the Organization field is labelled as a "locked" system field when i investigate the custom fields.

Any idea how I can fix this or must i create a seperate custom field on my software board?

Thanks

Comments

Jack Brickey

Hi Vanessa,

I may be missing your point here so if that is the case please redirect me. Organization is a Jira service management specific default field. It does not apply to JSW.

also may I ask why you’re moving tickets from JSM to JSW? This obviously will break the connection with the reporter/customer.

A A Ron Geister _Trundl_

I will second this. If you need to moving issues to JSW it is best to clone issue to the JSW project if it belongs to the dev team and or have them work on the issue as devs in the ITSM project.

Omar Hutchens_p9zrc4

I would agree, to second guess this. You are moving issues (tickets) from JSM and breaking the customer/service desk interaction.

If you are looking to bring in those tickets to a project board, consider creating a board in your desired JSW project and filter on that JSM project. Just an idea, but organizations (from my understanding) is only in a JSM feature.

Marc -Devoteam-

Hi @Vanessa Becker

Organisation is a JSM specific field. Any information in this field is only applicable to JSM projects.

If you want to retain this information into a Jira software project, you would need to create a new custom text field.

Other point is the same as @Jack Brickey raises, why do you want to move this issues?

The issues will loose the relation with the customer.

If these are issues that require effort from a backend team in you company, best practice is to create a linked issue in the Jira Software project. This to keep the relation to the customer with their raised issues and the backend issue.

Regards,

Marc

Welcome!

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