General

General

Categories

JUMP TO ANOTHER FORUM

  1. In the Items view, for a single file we have the (customizable) submenu "Open".

    In the History list for a single file, we have the "Save this revision as..." command along with "Open" and "Open with...".

    For consistency and ease-of-use, the "Open" submenu should be available in the 2D History view for a single file as well. Also, the "Save this revision as..." command should be added to this "Open" submenu.

    This is much related to another uservoice that requests adding the "Save this revision as..." command to the "Open" submenu in the Items view as well:

    http://plasticscm.uservoice.com/forums/15467-general/suggestions/5125416--save-as-from-browse-repository-on-this-changese

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We were using the VisualSVN plugin for Visual Studio before, and we miss the excellent "Quick Diff" feature: https://www.visualsvn.com/visualsvn/features/

    This feature replaces/enhances the "Track Changes" markers in the Visual Studio code editor with colored lines (in the left margin), to indicate blocks of lines that are changed relative to the latest changeset (different colors for modified, added, deleted). It also adds commands (revert block, navigate prev/next change block).

    There are some other (open source) plugins that offer similar functionality: "Git Diff Margin", "TfsPendingChangesMargin", "HgVS".

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. If you use a console based diff tool such as vimdiff it can cause the GUI problems. It would be nice to be able to set different difftool preferences for the GUI and 'cm diff', possibly with a command line option:

    cm diff --tool=vimdiff

    It might be necessary to give tools names or id's in the GUI preferences to reference from the command line so you can easily configure the arguments.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. It would be a nice feature to allow setting a color for elements.

    Examples:
    - set the label color red to mark it as "important".
    - set the branch color to green to indicate that the branch is the "test branch"

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. This is a new idea inspired by another uservoice that was declined:
    https://plasticscm.uservoice.com/forums/15467-general/suggestions/10300338-remember-last-entered-path-for-workspace

    However, the solution suggested here supports all three of the conflicting scenarios given by Codice staff when declining the earlier uservoice: a proposed initial default path (set on first install), a configurable root path (now set from GUI) and a way to remember the last entered path (but only on demand).

    There is a setting DefaultWorkspaceRoot in file guiclient.conf, but there is no way to set that from the GUI. I propose adding a link/button "Set as default path for new workspaces" or similar in the New…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Would you consider adding optional horizontal comparison panes to the diff viewer, displayed or hidden with a button or a key combination?

    It becomes useful when there are changes in long lines. Thanks to them you don't usually have to scroll the window in order to see all changed areas. This idea comes from WinMerge, which has both vertical and horizontal comparison panes.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Provide a mechanism to approve merges into specific branches.
    One option is to use pull requests with an approval mechanism (of one or more required approvals).

    This will allow trace-ability and enforcement of organization rules.
    Linking it to code review will make it even greater.

    (Check out Stash for examples)

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. The Branch Explorer "Options" sidebar has its "tabs" in a vertical layout, which works better when there are several tabs. Other sidebars (in the Branches and Changesets views) use horizontal tabs instead. It would make sense to unify these so the same type of sidebar component is used in all these places.

    Additionally, I think the "View History" view should have a sidebar as well...

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We are missing a two-way coupling between Plastic and the issue tracker (in our case Trac). If we have setup a Plastic WebUI, it would be nice if the Plastic issue tracker extension could add a WebUI hyperlink to the ticket comments when we create a branch from a ticket.

    This should be doable for Trac at least, since the extension already adds a comment to the ticket when "Mark as open in issue tracker" is checked during branch creation?

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. This would be very useful for learning and experimenting with the query syntax, and for quickly adding/adjusting a query without having to remember syntax.

    It should be possible to build the query by selecting the different targets etc and adding/removing/editing filter specifications. The resulting query text should be displayed.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Display a "+" or similar at left/right end of branch in Branch Explorer, when it has been truncated by the date-filter.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Window sizes for these windows are remembered the next time you open them, but adjusted heights of the splitter panes (comment, changes, diff) are not.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This currently only works for two Controlled files or two Controlled folders.

    It would be great to have this work for two Private files (or one Controlled and one Private file) as well. You would have to do some detection of txt/bin filetype on the Private files.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. User A changes revision type of an item from binary to text. User B runs update and refresh of items list, but item remains binary. Pressing CTRL+D shows a dialog that quotes "Error: Differences between items of diffente types cannot be calculated". That implies that the change of User A was sent to the server and applied to the item, but the information is not propagated to the other users.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. When the preference "Other Options - Show current Plastic SCM user in the window title" is active, it always displays the username configured under "Preferences - General". If there are connection profiles stored under "Preferences - Profiles", this may not be the same user that is logged in at the active workspace. It may not even be a valid user at all, since you will be transparently connected if there is a valid profile.

    To be really useful and accurate, the username displayed in the window title should be updated every time the active workspace changes - instead of blindly…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. When the Items view is in "List view" mode, there should be a context menu when right-clicking on the white background (as opposed to right-clicking on a file or directory). This context menu should display choices relevant to the "parent" folder we are looking into.

    Likewise, in the Windows Shell extension, the Plastic SCM context submenu that appears when right-clicking on the white background in Windows File Explorer should display choices relevant to the parent folder (the same choices you get if you go one level up and right-click on the folder in question).

    This is how Windows File Explorer…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Definition: when I refer to a repo "hiearchy", I mean some repo ("the top" level repo) and all of the repos xlinked below it (those repos may contain xlinks to repo, thus the "hierarchy").

    Today, if you have a large and complex repo hierarchy, it make it very difficult to work distributed.

    Use case: A "top" level repo than contains in it's referenced "repo hierarchy" 200-300 other repos via xlink. These other repos may be several levels of xlink deep. The purpose of all of the xlinks is component/reuse structure of coding.

    While creating such a repo on a central…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. The "Explain Merge" functionality is currently only available while performing a merge, and not in retrospect when looking at an existing changeset containing one or more merges.

    I suggest adding this functionality to the "Diff changeset" view as well. it could be activated by context menu on a "Merged from ..." changelist header.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. I know this was the default behavior a couple of versions ago, and it was extremely advantageous for our team because we tend to have a lot of files (XML data and such) that get changed but we don't intend to preserve those changes.

    We had been in the habit of checking in only our relevant changes, and it's been a big change to our workflow to have to either undo all pending changes first, or deal with the merges that ensue. If there was an option to prefer the old behavior it would be a big help!

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. In Perforce, you can branch an individual file to a new name, in a sense copying it - including history.
    This allows future trackback of changes through the file all the way to original files.

    Use case:
    Re-factor of source file to separate into multiple files.

    93 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?