Setup

Move Objects for Assets works on Jira Service Management Cloud with Assets. It moves Assets objects to another object type, in the same schema or another, and points every reference and work item at the moved objects.

Install

1. In Jira, go to Apps → Explore more apps and search for Move Objects for Assets, or open the listing on the Atlassian Marketplace.
2. Choose Get it now and start the free trial. Sites with up to 10 agents can use it for free.
3. A Jira administrator approves the install. The app appears under Jira settings → Apps → Move Objects.

The first time you open it, Jira asks you to Allow access: the app checks your own permissions and deletes old objects as you, so Assets applies your rights.

Who can move objects

• A Jira administrator,
• who is also an object schema manager of both the schema the objects come from and the schema they go to.

Only the schemas you manage appear in the lists.

Move objects

1. Choose the schema and object type the objects come from.
2. Choose the schema and the new object type.
3. Optionally, narrow it with AQL, for example Status = "In Stock". Leave it empty to move every object of the type.
4. Choose what happens to the old objects: delete them once everything points at the new objects, or keep them with their history and comments.
5. Select Check. You see how many objects will move, every attribute and where it goes, the attributes the new type does not have, and any reference that would refuse the new type.
6. Select Move and confirm.

Keep the page open while objects move. If you close it, the move pauses and continues from where it stopped the next time you open the page. You can Pause and Continue at any time, and Try the failed ones again when it finishes.

What happens to each object

1. Every object that references it is checked: if a reference only accepts the old type, the object is not moved and nothing changes.
2. The object is created in the new type with its attributes. Attributes the two types share are copied as they are; others are matched by name and kind (a text "Serial" never goes into a date).
3. Every object that referenced it now references the new object.
4. Every work item whose Assets field held it now holds the new object. No emails are sent.
5. The old object is deleted, or kept with its unique values cleared.
6. Unique attributes are set on the new object.
7. The move is written to the move log.

The move log

Open the Move log tab to see every move from the last year. Search by the old or the new key to see the values that did not fit the new type and the old object's history.

Before you move

• References. If an attribute on another type only accepts the old type, allow the new type on it (or its parent type with child types included), then check again.
• Required attributes. If the new type requires an attribute the old type does not have, make it optional or add it to the old type first.
• Assets imports. If an import (Assets Discovery, Jamf, Intune, a CSV import) keeps these objects up to date, point its mapping at the new type first, or the next import creates them again in the old type.
• Automation. Rules on objects created, updated or deleted, and Jira rules on Assets fields, run for each moved object.
• Work item fields. If an Assets field's filter scope only allows the old type, that object stops after its references move; widen the scope and try it again.

Limits

• Moved objects get new keys: Assets cannot change an object's type. The move log links old and new keys.
• Assets comments and attachments are not copied. Keep the old objects if you need them.
• Up to 2,000 objects per move, and 300 objects referencing any one object.
• Forge apps do not run in the Jira mobile apps; use Jira on the web.