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. Xlinks to single files (VSS style)

    We would like to convert from VSS to Plastic SCM, but VSS's file sharing works completely different than Xlinks in Plastic SCM (as far as I understood).

    1. Firstly, there needs to be a possibility of creating xlinks to single files, just like in VSS. It is really important for us. We want to share single code files and single binaries between projects. Sharing the whole project (as a repository) when only its binary file is needed (or several code files) is no solution to us :-(.

    2. Secondly, there should be two xlinks modes:

    3. A link to a specified revision -…

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Where do I report bugs?

    I get the following error

    Error

    Can't add an entry with the same name. Duplicated child [com]. Parent [localrepo]

    OK

    where do I report this bug? I have the latest version (4.1.10.372 - Brighton)

    1 vote
    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  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. History of permissions

    As PlasticSCM administrator, I want to have an history of the permissions changes on both server and repositories. And being able to roll-back and forth. (As for Git; the gitolite access-control layer is actually handled by a Git repository.)

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Make changeset comments editable.

    Sometimes I need to change the comment I made on a changset. As far as i can tell, there's no way to do it. Would be great to be able to. TFS has this feature.

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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.

  6. Add right click option to add files to ignore list

    i used to work with git and smartgit for the client tool.
    in smartgit i can select files and then add them to ignorelist using right click menu on the selected files.
    it is nice feature if you have this also.

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. 3rd Party comments

    It is possible to have 3rd party tools contribute text to the changelog?

    I'm thinking of tools like NArrange (which can totally re-arrange files) or FxCop that is usually a sign that warnings get fixed in bulk.

    It would be nice if these could could already prepare some of the changelog for a next check-in (I'm thinking of a simple message like 'tool x has run at timestamp y').

    It would be 'easy' to implement if the changlog textbox would pickup a predefined textfile when showing the checkin dialog to the user (and delete it after a checkin).

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Will you implement a french translation soon ?

    9 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. BUG: Branch explorer "Display only relevant changesets" error

    I've only had this happen intermittently, so unfortunately I don't know the exact repro conditions. I know which conditions MUST be true, but there are clearly other "sometimes" true conditions that are also required for this to happen... if I can discover more, I'll post.

    Known conditions in summary:

    If a user creates a new branch but does not have any changesets in the branch yet, and a second user is viewing branch explorer with "display only relevant changesets" enabled, branch explorer will generate an error when the second user attempts to refresh the display. An error popup will be…

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Add support for Seapine Test Track Pro Workflow and Issue Mgmt System

    I would like to see Plastic SCM have support for TestTrack Pro issue management system. See the following link to add support using TestTrack's SDK for C#: http://labs.seapine.com/wiki/index.php/TestTrack_SOAP_SDK_Tutorial_-_C_Sharp

    For more information on TestTrack, go here: http://www.seapine.com/ttpro.html

    33 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Provide a way to submit bugs on the product (aside from the forums)

    17 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Client GUI: Execute check-in in seperate thread.

    For the PSCM GUI, check-in's seem to take a long time meanwhile locking the main ui thread. Executing the check-in command in a seperate thread would be really nice and a progress bar to show at the status bar would be even better.

    19 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…)
    7 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Allow Xlinks to target branches in addition to changesets

    Xlinks in this way would point to the most recently committed changeset on the target branch branch, rather than just a specific targeted changeset. If need be this might have to be a read only Xlink.

    This added functionality, especially in conjunction with partial Xlinks, would allow for very dynamic repository creation.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Fix uninstaller.

    My VSS SCM got disabled when I uninstalled Plastic. the reason I uninstalled Plastic, is because VSS->Git->Plastic resulted in CRLF->LF in all files, which broke all DSW and DSP files (and others).

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. You're a liar!

    On the comparisons table, the second line already is wrong. Subversion does version directories, since the beginning.

    I did not bother to read any further then...

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    declined  ·  psantosl responded

    Mr. SVN lover,

    Subversion, since the very beginning, has suffered fom its inability to deal with simple merge cases involving directories.

    You move a file on a branch, modify it in another one.

    Run a merge.

    You get two files.

    This is basically NOT versioning directories correctly.

    Anyway, do yourself a favor and keep using SVN while the world moves away from one of the worst version control systems ever made.

    Regards

  17. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Branch synchronization in sync views

    In replication sync views it is only possible to define a whole repository as replication target.
    It would be nice also to be able to specify a branch subtree. This will be very handy when you want to make a light weight synchronization of a huge repository with a laptop or some other entity that doesn't need gigabytes of testdata or years of changeset history.
    I don't want to waste solid state space on my laptop to have an entire project history, though I do want that history to be available on the main server.

    1 vote
    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 3 4 5 7
  • Don't see your idea?