Wrong type? Move it.
Move Assets objects to another object type in Jira Service Management. Attributes come with them, and every reference and work item follows.
Free for up to 10 agents · Jira Service Management · Runs on Atlassian
A Jira Service Management app that moves Assets objects to another object type, in the same schema or another. Each object is created in the new type with its attributes, every object and work item that pointed at it is pointed at the new one, and the old object is deleted or kept. Everything is checked before anything changes, and a move log links each old key to its new one. It runs entirely on Atlassian, so no data leaves your site.
See the move before it happens
Choose the objects and the new type, then check. You see every attribute and where it goes, the ones the new type does not have, and any reference that would refuse the new type, before anything changes.
- Same schema or another one
- Only the objects your AQL filter matches
- Required and unique attributes handled for you
References and work items follow
Every object that pointed at the old object, and every work item whose Assets field held it, now points at the new one. Nobody is emailed and nothing is left pointing at an object that is gone.
- Objects that referenced it are repointed
- Assets fields on work items are updated
- A reference that only accepts the old type stops that object, untouched
Safe from the first object to the last
Objects move four at a time and every step is saved. Pause, close the page or lose the connection: the move continues where it stopped and never makes a second copy.
- Pause and continue at any time
- Failed objects can be tried again from where they stopped
- Only Jira admins who manage both schemas can move
Nothing is lost
Moved objects get new keys, so the move log links each old key to its new one for a year, with the values that did not fit the new type and the old object’s history.
- Search by old or new key
- Values that did not fit are kept
- Or keep the old objects with their comments
A look at the real screens
The real app in Jira, with sample computers. Open any screen to see it full size and zoom in.
Every attribute and where it goes, before anything changes.
1 / 3 · Moving objects
Everything Move Objects does
One app for every Assets schema on your Jira Service Management site.
Any type to any type
Move objects to another type in the same schema or another one.
Attributes come along
Shared attributes copy as they are; others are matched by name and kind.
References follow
Objects that referenced the old object point at the new one.
Work items follow
Assets fields on work items are updated, without emailing anyone.
Checked first
Nothing changes until every reference to an object accepts its new type.
Unique values kept
Unique attributes move to the new object once the old one is gone.
Delete or keep
Delete the old objects, or keep them with their history and comments.
Pause and continue
Every step is saved, so a move resumes and never makes a second copy.
Move log
Old and new keys, values that did not fit and the history, kept a year.
Filter with AQL
Move all objects of a type, or only the ones your AQL matches.
English, French and Arabic
The admin page in three languages, Arabic right to left.
Runs on Atlassian
Built on Atlassian Forge: no data leaves your site and nothing is stored outside Atlassian.
Pricing
Per agent per month, billed through the Atlassian Marketplace on your site’s Jira Service Management agent tier. Every plan starts with a 30-day free trial.
1–10 agents
Free
11–100 agents
$1.50
per agent per month
101–250 agents
$1.10
per agent per month
251–1,000 agents
$0.70
per agent per month
1,001–5,000 agents
$0.30
per agent per month
5,000+ agents
$0.15
per agent per month
Questions, answered.
Anything else? Contact support
- Not on its own: Assets Cloud has no move, only export and import or a clone rule that loses links. Move Objects does it: the object is created in the new type with its attributes, and every reference and work item is pointed at it.
- No. Assets cannot change an object’s type, so the moved object gets a new key. The move log links each old key to its new one, and you can search it by either.
- Every object that referenced the old object, and every work item whose Assets field held it, is pointed at the new object, without emailing anyone. If a reference only accepts the old type, that object is not moved and the check tells you which attribute to change.
- The check lists them before you move. Their values are kept in the move log with the old object’s history, and you can choose to keep the old object instead of deleting it.
- No. It is built on Atlassian Forge and runs entirely on Atlassian. It keeps a one-year move log on your site and sends nothing to Systematic or anyone else.
- It is free for sites with up to 10 agents. Larger sites pay per agent per month through the Atlassian Marketplace, from $1.50 down to $0.15 per agent as the site grows, with a 30-day free trial.