Under Community Review

Autocomplete in Publication Manager Should Include Options to Use Branches

The Autocomplete functionality in Publication Manager does not recognize branches, and does not offer them to users.

When a user attempts to roll up to the latest versions/branches of all files in a publication using AutoComplete, Publication Manager ignores the available branched files (3.1.1, etc), and even suggests that saved files using branches should revert to the previous full-number version.

This results in missed roll-ups and requires users to individually review all file versions and manually roll-up to later branches, as needed. This is time-consuming and error-prone.

The Autocomplete window currently contains these options:

-Latest released versions

-Latest available versions

-First versions

It would be helpful if the options were reworded and expanded to:

-Most recently released versions and branches

-Most recently available versions and branches

-Oldest versions and branches

Amy S
Parents

  • I'd disagree with this. The purpose of a branch is normally to perform a bug fix on a released version of content, and you specifically want to exclude bug fix branches on released content from updates to new (unreleased) content, which can contain new features. This proposal would confuse the difference between versions and branches.

Comment

  • I'd disagree with this. The purpose of a branch is normally to perform a bug fix on a released version of content, and you specifically want to exclude bug fix branches on released content from updates to new (unreleased) content, which can contain new features. This proposal would confuse the difference between versions and branches.

Children
  • in reply to Douglas Williams

    Thanks, Douglas. I hadn't considered that use case when I logged this request. We do not use our branches exclusively for bug fixes.

    Perhaps the options to include branches in autocomplete should be separate from the options to include versions? Our biggest concern is that Autocomplete doesn't recognize or include branches at all.