General
-
Sync, Repos and Workspaces on their own tab
Hi,
Since the latest release it's possible to close the tabs in the caption area.
Great feature but I would like one more enhancement, a non closeable tab (preferably the first tab on the right) that contains non workspace related subtabs like Your Workspaces, Your Repositories Rss Notification and Sync replication (not sure about Shelves).
This way the workspace related tabs stay cleaner (and smaller).
15 votesActually we started doing this on the new Mac and Linux GUIs :-) The new GameUI also supports this mechanism. Soon we’ll have it on the regular Windows GUI.
-
SCM Extension for Microsoft's Visual Studio Code
With v1.11.0 they've just publicly released the SCM API (https://code.visualstudio.com/docs/extensionAPI/api-scm), so it'd be greate to have Plastic integrated in this wonderful editor.
15 votes -
Synology NAS drive plugin for PlasticSCM server.
Create a plastic scm server plugin for Synology NAS to allow the server to be easily hosted on a NAS drive.
15 votes -
Number of active code reviews
please, add a number behind the code review menu item which shows the user how many active code reviews are assigned to him.
Maybe it could even flash up a bit when there are new reviews.
14 votes -
Add a context menu to the 'Checking pending changes' window
There is no context menu available for changed files in the 'Checking pending changes' window. However, there is a similar view in the 'Pending changes' tab of PlasticSCM's main window and a context menu is available there.
The thing is that the context menu enables you to view changes using a diff tool you prefer (the one set in application preferences). In the window mentioned in the topic there is no such menu at all and you can view changes only using the diff tool embedded inside that window.
Most of us in our company are used to WinMerge and…14 votes -
Show unchanged lines only for context in the text diff view
Option for the built-in diff window to show only a few (maybe configurable) unchanged lines around each changed line.
We have some multi-metabyte files with many thousands of lines and sometimes a few lines change and it is hard to scroll or click move around with such a large file. The buttons "to to next/previous change" are useful, but it is a lot more messy to actually see the diff.
See the attached file for a comparison with Araxis merge for an example.
In Araxis, we can see more information on the same screen.
13 votes -
Better issue tracker API
Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.
Create branch from ticket
I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made…13 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 -
provide an increased level of support for the eclipse ide platform.
Basically the visual studio plugin for PlasticSCM is very powerful, however the majorly popular Eclipse IDE open source platform plugin is very very limited. I'd like to see an increased level of support for this platform as I'm sure many others would as well.
13 votes -
Use "tab mechanism" from Branch Explorer sidebar in all other sidebars
The Branch Explorer "Options" sidebar has its "tabs" in a vertical layout, which works better when there are several tabs. Other sidebars (in the Branches and Changesets views) use horizontal tabs instead. It would make sense to unify these so the same type of sidebar component is used in all these places.
Additionally, I think the "View History" view should have a sidebar as well...
12 votesOur plan is to redo the windows GUI and implement what we already have on Mac and Linux… which is exactly what you’re asking for :-)
-
in file history change workspace
Add option to right click in file history to change the workspace to the changeset selected.
12 votes -
goto child changeset
In branch explorer there is a 'goto parent changeset' context menu. A similar one for children, possibly listing multiple branches, would be useful. Navigation is quite difficult in this direction.
12 votes -
12 votes
-
User License Control in LDAP Mode
Build an admin tool where users can be activated or deactivated in order to control user licenses in LDAP mode.
At the moment I do it manually. (Table seid, Column sactive)
12 votes -
Repository description
Add a description property to a repository and add it as a column to the repository browser to allow for a long description to give detailed information about the contents of the repo. Repo names tend to be short and don't always explain what the repo contains, especially when there are 100's of repo's for different projects.
12 votes -
Allow update-merge on "Update Workspace" and "Switch"
Back in old Subversion, the scenario of "Updating to a newer changeset (on the current branch) while there are Pending Changes in the workspace" was handled very smoothly and seldom caused any problems. (Sure, conflicts can arise but they are usually minor since we are on the same branch.)
I'm aware that it's recommended that each developer works on their own child branch. Nevertheless, this situation comes up, for example when two child branches are being concurrently merged back to the parent. Also, the Plastic team has already put some work into supporting this scenario:
http://codicesoftware.blogspot.com/2012/02/working-on-single-branch-update-merge.html
"While our recommended pattern…12 votes -
Add an option to prevent changing branches when you have added (private) files which are marked as pending adds.
This would prevent you from adding a file and forgetting to add it to source control before changing branch. This idea here is that you would set Plastic up to discover private files so you can see which files need adding. Any solution files or built data you would put in separate folders which aren't under source control and thus aren't detected by Plastic. This approach prevents you from forgetting to add files, i.e it'll build for you locally but not for others.
12 votes -
use the .gitignore file if it is present
Have plastic simply use the .gitignore file if it is present. Now that we support the online git repos like github bitbucket and VSO.
If you have .gitignore use that methodology and if you have .ignore use that methodology.
And maybe give user option to generate a .ignore file from a .gitignore.
12 votes -
Remember splitter heights in "Diff changeset" and "Explore changesets on branch"
Window sizes for these windows are remembered the next time you open them, but adjusted heights of the splitter panes (comment, changes, diff) are not.
11 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
11 votes
- Don't see your idea?