[RTFACT-8979] UI - Artifacts are moved to wrong folder Created: 11/Jan/16  Updated: 21/Jan/16  Resolved: 11/Jan/16

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Web UI
Affects Version/s: 4.1.3, 4.3.2
Fix Version/s: 4.4.0

Type: Bug Priority: Blocker
Reporter: Eric Düll Assignee: Roy Zanbel (Inactive)
Resolution: Fixed Votes: 0
Labels: None


If you select a "folder" that contains several versions and move it to a different repository, "Dry Run" works, but "Move" will move the artifacts to a wrong path.

Steps to reproduce:

  • Repository FROM_REPO contains two artifacts located in com/company/3rdparty-licenses.
    • com/company/3rdparty-licenses/1.36 (contains pom, source.jar, jar)
    • com/company/3rdparty-licenses/1.37 (contains pom, source.jar, jar)
  • open "Artifact Repository Browser" and select the parent folder com/company/3rdparty-licenses
  • In the upper right corner click "Actions > Move"
  • Select the new repository TO_REPO
  • click "Dry run" > everything is OK
  • click "Move" > erro message will be displayed
    • 1.36.jar and 1.36-sources.jar are moved to TO_REPO/com/company/3rdparty-licenses/3rdparty-licenses/1.36 artifact name became a new subfolder
    • 1.37.jar and 1.37-sources.jar are moved to TO_REPO/com/company/3rdparty-licenses/3rdparty-licenses/1.36
    • 1.36.pom and 1.37.pom remain both in the FROM_REPO


  • if you instead select the folder 1.37 and move that folder it works, but then you have to click on every version instead of moving a set of folders.
  • if you move a folder that only contains one subfolder it also works (e.g com/company/version/2.0 > select version and move it)


  • I don't really know a workaround. Before version 4.3.2 you could use the GAVC search, then stash the results and move the whole stash. That worked. But since 4.3.2 the GAVC search was removed.

Comment by Roy Zanbel (Inactive) [ 11/Jan/16 ]

Eric Düll Thank you for bringing this issue to our attention.
Please note that the GAVC search is still available under Package Search.
Also, I believe the issue described was resolved in version 4.4.0 when working on a related feature.

Closing the issue, please let us know if case this behavior reproduces on version > 4.4.0.

Comment by Eric Düll [ 21/Jan/16 ]

Thanks. It works with 4.4.1, could not test it with 4.4.0 as we had to directly install 4.4.1 due to some other issues.

Generated at Tue Aug 11 16:22:17 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.