General

General

Categories

JUMP TO ANOTHER FORUM

  1. Right now there is no mechanism to prevent users from deleting code reviews (unless I've missed something obvious), which is a problem for what we're trying to do. If nothing else it would be nice to have a "before-rmreview" trigger that we can hook into

    14 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 →
  2. The default ordering of branches in Branch Explorer could be improved. It should respect and make use of the branch hierarchy, so as not to cross lines unnecessarily.

    When I have several top-level branches with some child branches each, they are not grouped together vertically in a hierarchically logical order. Instead they seem to be randomly placed (?) leading to a lot of lines crossing each other. (I always enable "Display cross-branch changeset links" which makes this more obvious.)

    I think child branches should always be displayed below their immediate parent (or sibling if multiple children overlap in time).

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. On merge arrows, we can click and get a tooltip of info (changeset and branch of source and destination, respectively). We can also right-click and choose commands "Go to source/destination changeset".

    I suggest making the "cross-branch changeset links" (branch base/parent & child relation lines) clickable in the same manner.

    You could display the following tooltip info:

    • base/parent changeset number,
    • base/parent branch name,
    • child branch name

    Also, you could provide the following right-click commands:

    • Go to branch base / Go to parent changeset,
    • Go to child branch

    The first command would be much more intuitive than first locating and selecting the…

    14 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 →
  4. Basically the visual studio plugin for PlasticSCM is very powerful, however the majorly popular Eclipse IDE open source platform plugin is very very limited. I'd like to see an increased level of support for this platform as I'm sure many others would as well.

    13 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 →
  5. Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.

    Create branch from ticket
    I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made…

    13 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 →
  6. In branch explorer there is a 'goto parent changeset' context menu. A similar one for children, possibly listing multiple branches, would be useful. Navigation is quite difficult in this direction.

    13 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 →
  7. It would be very helpful if there was a means by which certain directories/paths could be moved from 1 repository to another, complete with history.

    13 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 →
  8. If i have items or xlinks specified in cloaked.conf, the only way to force an update of these is to:

    • either removed them from cloaked.conf before "Update workspace"

    • or run "cm update --cloaked <path>" from the command line.

    NOTE: Contrary to old documentation, running the "cm update --forced <path>" command will not update cloaked stuff.

    I suggest adding a "Update Cloaked" command to the context menu in the Items view. Maybe also an "Update Forced" command, but this is probably less important.

    13 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 →
  9. Let the user undo a checkout without loosing the modifications themselves. The result would be a file with status "Changed".
    Neither the content nor the file's timestamp should change by this operation.
    Currently, undoing a checkout always results in downloading the versioned content.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Option for the built-in diff window to show only a few (maybe configurable) unchanged lines around each changed line.

    We have some multi-metabyte files with many thousands of lines and sometimes a few lines change and it is hard to scroll or click move around with such a large file. The buttons "to to next/previous change" are useful, but it is a lot more messy to actually see the diff.

    See the attached file for a comparison with Araxis merge for an example.

    In Araxis, we can see more information on the same screen.

    13 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 →
  11. I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.

    Our use case:

    We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.

    As…

    13 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 →
  12. Add option to right click in file history to change the workspace to the changeset selected.

    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 →
  13. 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 →
  14. With some (external) repositories last changes are sometimes so long ago that nothing shows up in for example the xlink changeset selector.

    So please show at least the last release if the query does not return results. This behavior should also be implemented for other query based views. Maybe with a switch in the preference to turn it on/off.

    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 →
  15. 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 →
  16. Back in old Subversion, the scenario of "Updating to a newer changeset (on the current branch) while there are Pending Changes in the workspace" was handled very smoothly and seldom caused any problems. (Sure, conflicts can arise but they are usually minor since we are on the same branch.)

    I'm aware that it's recommended that each developer works on their own child branch. Nevertheless, this situation comes up, for example when two child branches are being concurrently merged back to the parent. Also, the Plastic team has already put some work into supporting this scenario:
    http://codicesoftware.blogspot.com/2012/02/working-on-single-branch-update-merge.html
    "While our recommended pattern…

    12 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 →
  17. This would prevent you from adding a file and forgetting to add it to source control before changing branch. This idea here is that you would set Plastic up to discover private files so you can see which files need adding. Any solution files or built data you would put in separate folders which aren't under source control and thus aren't detected by Plastic. This approach prevents you from forgetting to add files, i.e it'll build for you locally but not for others.

    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 →
  18. I like to have my branches ordered bottom-up as they are closest to release. So my issue branches are below the trunk which is below release candidates and hotfix branches.

    I do this manually right now. So I have two lines für release/hotfix branches then the trunk and then everything else.
    This is fine as long as there are only 2 branches in the upper two lines. But sometimes there are more (especially when 'older' branches are updated with new data. Then they overlap.

    My suggestion:
    Add a weight property to branches (maybe via conditional rules) and order the branches…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. The new "multi-screen diff" in Plastic 6.0 is excellent. It was introduced in 6.0.16.884; if you have the Plastic SCM main window open on part of your screen, and open one diff window on another part of your screen, then the diff window's contents will change when you move around in the Branch Explorer.

    (Slightly related uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/15615156-show-diffs-in-branch-explorer-and-changesets-views )

    However, this has a few flaws related to cases where you don't want the "Diff changeset" window to change. To stop the Diff from updating when you click a changeset, you need more than one Diff window open. This is OK…

    12 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 →
  20. Using a dark theme with the linux build ends up with some pretty glaring white backdrops to things and lots of unreadable text.

    It seems Plastic isn't using the supplied gtk theme colours, but instead has hardcoded colours for certain things.

    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 →
  • Don't see your idea?