526 results found
-
Different Branch Explorer filter config for each workspace
Today configuration data (include filtering) is global for Plastic. It will be great if it was different for each workspace (that will allow use different filtering configs for each repository).
5 votes -
OAuth2.0 Authentication with Azure AD
Azure Active Directory implementations offer an OAuth 2.0 Service endpoint for authorization. Being able to use this as an authentication option for the Plastic server could be a great addition to the product.
1 vote -
create shelve from changeset
You should add a way to shelve a already checked-in changeset. This way a checkin on the wrong branch could be shelved, deleted and then applied to the correct branch.
33 votes -
Improve usability of the embedded code review system
The code review system is very basic but I believe a few simple things can make it much more usable. I submit a list of them here: http://www.plasticscm.net/index.php?/topic/2276-suggestions-for-code-review-system
59 votes -
Different display settings for 2 workspaces that refer to the same repository
I have 2 workspaces that refer to the same repository. To get an easier view of the diagram, I tried to set the display options differently to show particular branches for each workspace. It seems imposible to have different display settings
3 votes -
Add Bisect Feature
One big feature of SCM is to hunt down where / when a bug is introduced. It is done through a bisect feature:
http://en.wikipedia.org/wiki/Bisection_(software_engineering)
Maybe PlasticSCM should implement the feature as well?
9 votes -
Add ability to color label captions
Currently label captions are light gray and are hard to read. It would be great if there was an ability to change their color to more contrast one, or add customizable back color like branch captions
7 votes -
Have a mechanism to split repositories
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 -
Change changeset being compared.
XCode has a nice feature during comparing files.
It lets you change the one on the right side (so the one from version control with a slider),
The effect is that you can easily find the spot in time where something has changed. Such feature would need the positions in both files to remain stable (so not jump to the top).
6 votes -
Drag and drop files from Windows Explorer. Like Perforce etc. Let Windows do what it is good at.
I really miss the drag and drop functionality that most Windows programs have such as Perforce. I'd like to be able to drag files from a windows explorer window to a changelist etc.
26 votes -
Commenting xlink changes in code review
"Xlink changes cannot be commented" - that message shows up when you try to comment a change in an xlinked file (in a code review). IMHO it would be much easier if xlinked files could be commented just like other files.
122 votes -
Plugin for SQL Server Management Studio (SSMS)
A plugin to allow integration of the following features in SSMS:
-change commits
-annotated files
-revision history on a file
-workspace explorer
-branch explorer3 votes -
Automatic comments based on semantic changes
I would love the ability to select a new button "auto comment" from Checkin Comments drop-down on the Checkin UI that would use the the semantic code engine to generate comment lines like the following:
-added update methods to InquiryRepository
-added Username parameter to SetReferralDelivered() in ReferralService
-deleted class MyFakeClass
-created new enumeration MyFakeEnumthis would be the basis of every checkin comment and then the developer could add to it with specifics or just modify the text to be more explicit or supply reasoning or whatever.
6 votes -
Add git like staging
I encountered on several occasions already that what was displayed in pending changes did not match the actual state of files being committed. The reason being that changes are not automatically updated in the UI, but upon commit new changes are automatically collected using default behavior of changed files being committed, added, moved and deleted files must be selected manually - meaning the latter will not be part of such commit. The minimum thing that could be done is to notify the user that there are undisplayed changes that need to be reviewed. Even better would be to add git…
24 votes -
Open double clicked file in pending changes in visual studio plugin.
When viewing the "Pending Changes" in Visual Studio plugin, double clicking a 'changed' item opens the 'Diff view'.
I think that when you double click a file it should open the file editor. This will make the behavior more consistent with Visual Studio in general and with the behavior of double clicking an 'added file'...
It will also make it more consistent with the behavior of other source controls, making the transition to Plastic even smoother.
9 votes -
Support for more complex find queries
Specifically, I want to find all changesets with two attributes with specific values. Something like:
find changesets where attribute = 'Review status' is 'none' and attribute = 'Reviewer' is 'somebody'36 votes -
file history improvements
1) highlight the current file revision in the history list GUI & command line as selected by the workspace (I had a feeling it was bold but isn't in 5.0.44.581). If the workspace revision is modified, the parent should still be highlighted.
2) give an indication of which revisions have been merged in the history list (eg. a column for number of branches seeing this revision; merged yes/no)
3) populate the 'Properties' panel when selecting items in the 'Version tree' (it is blank regardless of which branch or cs I select, and many of the cs numbers and names on…9 votes -
Icon for files added to source control but not checked in
Icons in Windows Explorer for files that are currently added to source control but haven't yet been checked in.
3 votes -
Secure code reviews
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 -
Provide scripts for diff and merge of Open Document Format files (odt, ods and odp)
Currently there are merge and diff scripts available for xls(x), doc(x) and ppt(x) files, but more and more European organizations are moving to Open Document Format files as their standard.
4 votes
- Don't see your idea?