526 results found

1. Add button "Set as default workspace path" in New Workspace dialog

   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 Workspace dialog, next to the workspace path box. When you press that button the mentioned setting should be updated with the currently entered workspace path (minus the filename). That way a user will not have to manually edit this setting in the .conf file, but on the other hand it will not be overwritten if you temporarily use another path for a new workspace.

   NOTE: This feature would be similar to the "Set as default query" used elsewhere in the GUI, so it should be consistent with the overall style...

   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… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Horizontal comparison panes in diff viewer

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Pull Requests

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Use "tab mechanism" from Branch Explorer sidebar in all other sidebars

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   planned  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

   Our plan is to redo the windows GUI and implement what we already have on Mac and Linux… which is exactly what you’re asking for :-)

5. Issue tracker: add WebUI hyperlink to ticket when creating branch

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Implement a simple popup editor for designing "cm find" queries

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Indicate date-truncated branch in Branch Explorer

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Remember splitter heights in "Diff changeset" and "Explore changesets on branch"

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Items view: allow Diff of Private files as well

   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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Bug: Revision type change is stored on server but not updated on clients

    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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Follow active workspace when showing user in window title

    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 displaying the username stored in "Preferences - General" it should displayed the user that is actually connected to the server for the currently active workspace (the active workspace tab).

    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… more

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Add context menu on "background" in Items List view (and Windows Explorer)

    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 normally works and I think Plastic should follow these conventions.

    Here's a usage scenario:
    * In the Items view, enable the "List view" mode button.
    * Drill down into a sub-folder.
    * Right-click somewhere in the empty (white) space below or to the very right of the displayed items. No context menu appears.
    * NOTE: If you had done similarly in Windows File Explorer, a context menu would have appeared concerning the parent folder.
    * As it is now, there is no way to perform an action on the parent folder (create xlink, view history etc) except by either going up one level or switch to the "Tree view" mode.

    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… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Support for working DVCS with a repo "hierarchy" and easy local repo creation/sync

    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 server, and having everyone work on the repo hierarchy on the central server is fairly straight forward, it is extremely difficult for someone who would like to be able to setup to work with this repo hierarchy using DVCS. I can make sure each xlink is "relative" so that it does not depend on being able to see the central server, but that does not address the following problems in setting up a sync to my local PC:
    1) I need to determine the entire list of xlinked repo names, and recreate each of those repos locally (keeping the names the some or the relative xlinks will not work even after sync'd).
    2) I now have to setup a sync and add each source/destination pair for each of the 200-300 repo in the repo hierarchy. All of this is doable, but very tedious and error prone.

    One proposed solution to this use case issue: Have a way that either during sync setup, and/or during sync itself to:
    a) Create any local repo needed to correspond to any of the repos in the repo hierarchy (top repo listed in the sync and all xlink'd repo below in the hierarchy).
    b) auto-sync (or option to sync) all repos in the hierarchy just by adding the top level repo to the sync pair (sync'd to the same named local repo).

    Whatever the method, it need to account for the fact that the repo hierarchy (which repos are referenced by xlinks in the hierarchy) can and will change over time (at least added to).

    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… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Reuse the "Explain Merge" view for existing changesets

    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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Include a preference to override all unchecked pending changes in workspace on check-in.

    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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. File "branching" to allow new file to track inheritance from previous file

    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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Have option to have to confirm a check-in operation. The use case is that because the refresh pending changes button and the check-in butto

    Have option to have to confirm a check-in operation.

    The use case is that because the refresh pending changes button and the check-in button are so close together, some users accidentally click the Checkin button when they mean to click the refresh.

    Some users would certainly find the extra confirmation annoying, so if implemented, this should definitely be an option controlled via Preferences.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Add "Diff selected items" to shell extension as well

    In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This option should be available in the Windows shell extension as well.

    The following related uservoice should apply here too:
    http://plasticscm.uservoice.com/forums/15467-general/suggestions/10027482-items-view-allow-diff-of-private-files-as-well

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Smarter loading of changesets in "Explore changesets on this branch"

    When selecting "View - Explore changesets on this branch", sometimes the message "This branch has a large number of changesets ... Continue?" pops up AFTER a lengthy calculation and if "Yes" is pressed, the "Branch Changes" window is then displayed instantly! ;)

    Taking a hint from TortoiseSVN, you could load only the latest 100/1000 changesets or so, and then have buttons to "load 100 more" and/or "load all"...

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Switch/Update should include metadata for cloaked items

    As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.

    If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.

    Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items in the same directory and you want to update just one of them. (If metadata is fetched you can perform a "cm update --cloaked <item>" to update just one item at a time. However, if metadata is not yet available you can only do the update on the parent folder, which would update all the cloaked items at the same time.)

    I suggest always fetching metadata for cloaked items, to improve consistency. For cloaked folders, it would be sufficient to fetch metadata for the folder itself, not for the sub-tree below it (for performance reasons).

    As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.

    If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.

    Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items… more

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close