152 results found
-
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 votesThis 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.
-
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 -
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 voteNever heard of it again, didn’t get any more votes either.
-
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 voteInteresting, but nobody else was interested on it for 3 years… so we have to clean up the list and focus on what people really want.
-
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 voteThere is already a way to do it! :)
-
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 voteWe already support this, don’t we?
-
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 -
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 voteNot reproduced. No more info requested to the submitter.
-
9 votes
Didn’t hear back from the volunteer in years :O
-
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 voteMr. 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
-
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 voteWe added “ignored branches” for this purpose on sync view long ago :-)
-
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 votesWe can’t break cset immutability.
-
Visual Studio integration crashes at some point and requires restart to continue working
While working in VS 2010 (run as Administrator) at some point while trying to do a checkin I get a message like:
"The type initializer for '196379271' threw an exception.
Method not found: 'Void 1829760192.1231065091(1909317638,Mono.VisualStudio.TargetAddress)'."From this point on I have to restart VS or use the stand alone client to do anything with Plastic.
I get a message like: "Another operation is already running".
3 votesWe haven´t been reported a similar issue again. In future, please report the issues at: www.plasticscm.net
-
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 votesNever heard back from supporters :’(
-
Improve the error message when the name of the branch to checkin changes contains "/"
Currently Plastic says that the the branch you selected to create and use to checkin the changes there does not exist?!?!?
If you try to create it without checking in anything you don't get any messages and nothing happens.
It would be best to warn the user that the branch name contains forbidden character.
1 voteUnable to reproduce.
-
17 votes
We use private UserVoices with some customers. In general we optimized the way in which release notes are displayed in Q4 2014, so everything is much clearer now.
-
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 voteIt is an issue with the git export.
-
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 votesWell, when you delete the repo you should leave the system in a consistent status so that the db admin can go and really remove the database…
-
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 votesThe bug tracking system comment is being shown near to the branch name in the branch explorer view
-
highlighting of un-merged branches
I wanted to be able to quickly see (within the branch explorer) branches that have changesets after the last merge in the branch.
An enhancement could be to do this only for child branches of a specific branch.As I described here:
http://www.plasticscm.net/index.php?/topic/876-highlighting-un-merged-branches/page__fromsearch__133 votesThere’s a rule in branch explorer specifically created to do that :-)
- Don't see your idea?