#1025 missing default volume symlink for imported builds affected by volume policy
Closed: Fixed 3 years ago Opened 3 years ago by mikem.

When a build is imported and placed on a non-default volume by the volume policy, the system does not create a symlink on the default volume pointing to the correct location, as it does when a build is moved across volumes. For consistency and convenience, we should fix this.


I'm going to work on this some today

Metadata Update from @julian8628:
- Issue set to the milestone: 1.17

3 years ago

Metadata Update from @franzh:
- Issue set to the milestone: 1.16.1 (was: 1.17)

3 years ago

Login to comment on this ticket.

Metadata