Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Aspera Ideas
Created by Guest
Created on Mar 7, 2023

Connect: Improve Aspera Connect folder creation feature

Proposal: Aspera Connect downloads should always obey the transfer spec `create_dir` and `destination_root` properties and behave consistently, whether the user relies on a pre-set base download directory or interactively chooses a base download directory when "Always ask me where to save downloaded files" is enabled.

The current behavior for a download with a transfer spec that includes `{"create_dir": true, "destination_root": "download-1"}` is very different depending on whether the user has configured Aspera Connect to always use a certain base download directory or has enabled the "Always ask me where to save downloaded files" setting.

If that setting is not enabled, and the download directory is configured as `/downloads`, then two files named `file1.txt` and `file2.txt` with a transfer spec that includes those settings will result in the following structure after the download completes:



If the "Always ask me where to save downloaded files" is enabled, and the user chooses the `/downloads` directory, then for the same transfer spec, the `destination_root` directory gets created but the files don't get downloaded into that directory, so it remains empty and the following structure is created:




The proposal is for Aspera Connect to behave the same in these two cases, so that regardless of whether the user chooses a base download directory each time or always uses the same base download directory (whether the default or not), Aspera Connect behaves consistently, with the following result:



The API documentation currently implies that it works the way I'm proposing it should work, and there is no mention of the very different behavior in the two cases, but Aspera Engineering is adamant that it's supposed to work as it does currently.

The reason it's important to support this is that it's very common to want all files of a single download to be downloaded to a custom subdirectory with a name provided by the server that is not known by the end user, and this is only possible currently if the user does not use the "Always ask me where to save downloaded files".

Idea priority Urgent
  • Guest
    Apr 13, 2023

    Hi there. Thank you for this feedback. I'm looking into this and will get back to you.

    Wishing you well,


    A.S. Behn, Technical Product Manager, IBM Aspera