Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

152 results found

  1. Add XML to SemanticMerge

    Seems many people save xml files as 1 huge long string. This makes line by line comparison rather worthless. If SemanticMerge could parse xml this would make comparison and merge of xml files so much better.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  2. visibility per workspace

    It would be nice to be able to define visibility rules per workspace and not per repository.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  3. Add "Cleanup workspace" command in Items view and Shell extension.

    For us, a common operation is that we have run compilation etc in a workspace and then want to wipe out all the generated output files to get a clean workspace again (similar to "make clean" in a Makefile).

    This is a feature I miss from TortoiseSVN, which has a context command "Clean up". What that command does is to bring up a small dialog with cleanup-options, where I can choose things like these (translated to Plastic nomenclature):

    • Refresh shell overlay icons

    • Delete private items

    • Delete ignored items

    • Undo all changes

    • Undo unchanged

    • Apply cleanup to xlinks as well

    Perhaps…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  4. Version 4 should have VSS import

    Please port the v3 vss import wizard to v4.

    The route by vss2git failed big time probably on a binary in vss. The route by svn is also far from flawless (I could not even exportmy error free vss to svn).

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  5. Show bug tracking system comment near branch comment in branch list

    or at least allow an easy way to set the branch comment to be equal to the title of the bug when creating the branch. (maybe us it as a default).

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  6. Drag and Drop compare from the BranchExplorer or Version Tree View

    You already offer "Diff with other ..." from the context menu, but making it drag'n'drop would make things even easier.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    declined  ·  0 comments  ·  Admin →

  7. Provide Comprehensive Documentation

    Most of Plastic SCM's documentation exists in the form of blog posts and tutorials. It's scattered and incomplete.

    Every command-line option, and every location and schema for every configuration file, should be documented online. Check out Docker's website - that's a great example to aspire to.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    9 comments  ·  Admin →
    declined  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

    We need more specific feedback to act.

    We are trying to reduce the number of config files, and in fact, everything should be configurable from GUIs, which is what most users want (we also got requests saying, no, I don’t want to learn a config file). GUIs or WebAdmin.

    So, maybe the setting you’re looking for (we don’t know which one it is) is not meant to be directly set on a config file, not sure.

    Anyway, our official docs are available here:

    https://www.plasticscm.com/documentation

    Not a bunch of blogposts :-)

  8. Please implement custom Checklis like the VCS in Rider

    Custom Checklist is very useful if you can't setup files to ignore.conf or hidden_changes.conf

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  9. Check in to other branch fails

    I had some changes, then other changes were committed, I tried to check in to another branch, it failed, I updated to the latest changes, tired again check in to another branch, it sent my changes but to the current branch and no new branch was created.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  10. use the recycle bin whenever you can

    On Windows, whenever you can, use the recycle bin.

    For example, before you've checked in a file to Plastic, and it's a pending add - if you right click on the file and click delete, it gets removed from the HD.

    It would be great if one of the following was done:

    • always use the recycle bin for when deleting files from the HD
    • have two options "Delete" and "Delete (via Recycle Bin)"
    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  11. Remember settings (like whitespace view) between Diff viewer sessions

    Currently (using 5.0.44), settings like "Comparison Method" for whitespace are not respected for more than one Diff session.

    This means that if you have a lot of whitespace changes that you want to ignore, you have to keep resetting this option every time you view a new diff (or even close and re-open a diff of the same file)

    Settings like these should be automatically applied as defaults when changed (or at least have a "use current settings as defaults" option in that menu).

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  12. Allow readonly xlinks to be created against labels

    If you allow readonly xlinks to be created against a label (rather than a specific changeset), this would allow for "dynamic" links in that if/when a label is moved, the corresponding xlink would be automatically updated with the new view of the source when an "update" operation is performed on a workspace against a branch that has such an xlink in it.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    declined  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

    This breaks the concept of Xlink.

    Trees in plastic are immutable. Every change must be tracked with a new cset.

    Doing what you mention is a way to avoid builds to be reproducible: just move the label and something “weird” will happen and you cset that used to build won’t build anymore.

  13. Please fix annoying error popup

    An error popup randomly opens when I check in, explore branches or whatever.
    If I click 'ok' button then same error popup opens again.
    The only way I can fix this is kill the process.
    I'm very frustrating with this bug. Please fix.

    2021-04-13 16:47:26,710 DESKTOP-PARK\PARK DEBUG GlobalConfig - Getting the repository spec for workspacepath 'c:\Space5'
    2021-04-13 16:47:26,712 DESKTOP-PARK\PARK DEBUG GlobalConfig - Getting the server config for repository spec 'Space5@MUMOSTUDIO@cloud', folder 'workspacetree', config file 'filetypes.conf'
    2021-04-13 16:47:26,713 DESKTOP-PARK\PARK WARN filters - PathValueMatcher: Error parsing line: # Plastic SCM extensions file. Syntax: <expression>:<type>.
    2021-04-13 16:47:26,713 DESKTOP-PARK\PARK WARN filters - PathValueMatcher:    …

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  14. 'cm diff' should compare a file against previous revision by default

    'cm diff' compares against the last checked in revision if the file is modified in the workspace. If it is not, it just gives a message "Item has only one revision". It would be more useful if in this case it compared the last two revisions. Finding appropriate revision numbers on the command line is not easy.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  15. Export Branch Explorer to Image (png/jpg).

    It's nice to capture a full-resolution (zoom=1) snapshot of the current BranchExplorer view for a number of reasons like presentations, sprint celebrations, framed photos for product milestones etc.

    In most cases I have to zoom out to an unacceptable level to see a couple of weeks of work on the branch and having a full-res image would help.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  16. Xlinks break when their target repository is renamed

    Repository A has an xlink to repository B. Repository B is renamed to C. When downloading the content of repository A to a workspace, there is an error, because the xlink points to a repository B that is no longer accessible under that name, even though it still exists.

    I know you rarely change repository name, but it happens. You can of course fix all xlinks after you do that, but you won't fix the history. So if you attempt to download a historical changeset of repo A, you won't get its whole content.

    Don't you think it would be…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Admin →

  17. Hide old branches

    We have some very old branches, which don't fit in our current branching concept. These where created when we first started using plastic scm and didn't know how to structure them.

    We do have a very clean structure for our branches - finally. In the "Branches" view all branches are displayed, no date filter is applied by default. We use the tree view, as it supports our branch structure very well. The only problem is: There are these old branches, which destroy the clean look and feel of our sturctur and also confuse some users.

    It would be nice to…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  18. License information on home screen

    I would like to access the license information, and be able to add a new license, from the first screen where I can select diff or merge.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  19. Keep info on deleted databases

    The lrep command (and the repositories database) do not contain any information on deleted respositories, making it hard to deterimine the repository name of a removed/deleted repository database for restoring.

    But if i want to restore an old one knowing which one it was might be handy. Is it an idea to add a boolean column mounted to the repository table in the repositories database (so you have record of old ones and can restore them 'more' easily)?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  20. Stop storing information in Visual Studio Solutions

    Many companies (mine included) don't store our projects and solutions within source control. There are many reasons for this, but in a nutshell, the VS formats don't play nicely when it comes to large, complex merges. Instead, we use things like Premake and CMake to generate our projects and solutions on developer machines. This is fundamentally incompatible with your VS integrations. Could there possibly be an option to store the information your tool needs in another format?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
2 4 5 6 7 8
  • Don't see your idea?