531 results found
-
Include a preference to override all unchecked pending changes in workspace on check-in.
I know this was the default behavior a couple of versions ago, and it was extremely advantageous for our team because we tend to have a lot of files (XML data and such) that get changed but we don't intend to preserve those changes.
We had been in the habit of checking in only our relevant changes, and it's been a big change to our workflow to have to either undo all pending changes first, or deal with the merges that ensue. If there was an option to prefer the old behavior it would be a big help!
22 votes -
File "branching" to allow new file to track inheritance from previous file
In Perforce, you can branch an individual file to a new name, in a sense copying it - including history.
This allows future trackback of changes through the file all the way to original files.Use case:
Re-factor of source file to separate into multiple files.93 votes -
Have option to have to confirm a check-in operation. The use case is that because the refresh pending changes button and the check-in butto
Have option to have to confirm a check-in operation.
The use case is that because the refresh pending changes button and the check-in button are so close together, some users accidentally click the Checkin button when they mean to click the refresh.
Some users would certainly find the extra confirmation annoying, so if implemented, this should definitely be an option controlled via Preferences.
1 vote -
Add "Diff selected items" to shell extension as well
In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This option should be available in the Windows shell extension as well.
The following related uservoice should apply here too:
http://plasticscm.uservoice.com/forums/15467-general/suggestions/10027482-items-view-allow-diff-of-private-files-as-well3 votes -
Smarter loading of changesets in "Explore changesets on this branch"
When selecting "View - Explore changesets on this branch", sometimes the message "This branch has a large number of changesets ... Continue?" pops up AFTER a lengthy calculation and if "Yes" is pressed, the "Branch Changes" window is then displayed instantly! ;)
Taking a hint from TortoiseSVN, you could load only the latest 100/1000 changesets or so, and then have buttons to "load 100 more" and/or "load all"...
6 votes -
Switch/Update should include metadata for cloaked items
As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.
If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.
Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items…
6 votes -
Unify buttons for toggling sidebar
In Branch Explorer / 2D Version Tree, replace the "Options" toggle button with the same "Show extended information" icon button as in other views.
Also, make the "Show extended information" icon button a "toggle button" in all views.
1 vote -
Display branch comments along with merge-info when viewing Changes
When creating a branch from an issue tracker task/ticket, the ticket title description is added as the branch comment.
When merging back from such a branch it would be very useful if the branch comment was displayed in Pending Changes (along with the branch name on the Merge Link and on the title of the Merge Changelist). Otherwise you only see the ticket number from the branch name (/main/trac5877 or similar).
The same goes for the Diff Changeset view, and possibly some other views as well. Display the branch comment along with each merge changelist header.
3 votes -
Improvements to the "Branch history" table in Branch Properties
There are a couple of things I'd like to see added in the "Branch history" table inside the Branch Properties view:
The "Source changeset" cell for the "Creation point" row should include the source branch, just as for the "Rebase from" rows. This would make it easier to see where a top-level branch was forked from, and even for child branches it would be more consistent. (Only changesets on the current branch should omit the branch name.)
In the context menu for the rows in this table there are "Diff ..." and "Browse ..." commands. I'd like add 2 more…
3 votes -
"Create submodule" to repo context menu
I'd like to add submodules to repositories by right clicking on the repo. I would then type the name of the submodule (i.e. <submodule>), only, instead of typing <reponame>/<submodule>. This avoids possible typos when typing <reponame>.
4 votes -
automatically update workspaces overview upon new workspace from repo
Client shows all repositories.
User selects one and executes "Create workspace for this repository"
A new workspace will be created.
User switches to workspace overview.
The new workspace isn't shown until user hits F5. The workspace overview should automatically being updated.1 vote -
Plastic SCM should show the relative git commit hash on the Branch Explorer Options window
It would be really nice for us who are using the GitSync feature to be able to know in Plastic the Git hash of a changeset. :)
6 votes -
Add Refresh (F5 key) for Differences
I believe there is a similar feature to refresh the diff window if it's open in the Pending Changes view. It would be nice if there was a refresh button/key inside of the Diff tool itself as well when it is already open in its own window. Having it refresh from the Pending Changes window will help a lot though if this is already working.
9 votes -
Fix the NPE in the IntelliJ plugin
When you run the plastic wizard inside IntelliJ there is an NPE at the page where you can select your workspace. See also attached file. This should be fixed.
1 vote -
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 -
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 -
After a Code Review for a branch, add an icon (e.g. a check, a pending sign, ...) to the branch in Branch Explorer
After a Code Review for a branch, add an icon (e.g. a check, a pending sign, ...) to the branch in Branch Explorer
105 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 -
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 -
diff view: Implement DRAG functionality on file paths of old and new files to be able to drag the files to another tool.
diff view: Implement DRAG functionality on file paths of old and new files to be able to drag the files to another tool.
You have a copy to clipboard on right-click already so this is a trivial change for you.
Add another option to the right-click, or what-ever, to allow users to DRAG the old FILE (since you already have it in the tmp directory) to another application ( beyond compare, windows file explorer directory, etc).
Do the same for the new file side also.
This way users can set a diff of the files they want then EASILY get…
1 vote
- Don't see your idea?