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

Parents
  • This is a request for the addition of branch-related functionality, not a replacement of the current version-related functionality.

    The suggested Autocomplete options are:

    -Most-recently released versions

    -Most-recently available versions

    -Oldest versions

    -Most-recently released branches

    -Most-recently available branches

    -Oldest branches

Comment
  • This is a request for the addition of branch-related functionality, not a replacement of the current version-related functionality.

    The suggested Autocomplete options are:

    -Most-recently released versions

    -Most-recently available versions

    -Oldest versions

    -Most-recently released branches

    -Most-recently available branches

    -Oldest branches

Children
No Data