535 results found
-
25 votes
-
gather all checkin comments since the last merge
I know this goes against the branch per task ideology, but sometimes people work on a bunch of stuff in a branch and then merge a larger chunk of work, e.g. a bunch of helper functions etc.
It would be nice if there was a way in the GUI to automatically gather all checkin comments since last merge / branch creation into the merge comment. I could then edit this comment before merging.
So for example if I make checkins "fix foo" and "fix bar", my merge comment would be "fix foo\nfix bar".
4 votes -
add a keyboard shortcut for "switch workspace to this branch"
Similar to "make active workspace" in workspaces, there should be a keyboard shortcut for switching branches.
2 votes -
Show the current branch in Workspaces overview
Currently, in the Workspaces overview, you only have columns for "Name", "Path" and "Repository". It would be nice to have another column "Current Branch".
This would make it easier to identify the correct workspace for a certain branch when having multiple workspaces with varying branches.
7 votes -
Retain checkin comments after having to merge before checkin
This happens all the time. You do some modifications, hit checkin, get told you need to merge beforehand, you do that and it's all automatic and nice and then you hit checkin again and notice the comments are gone.
The comments are of course in the history, but I have had to edit them exactly 0 times after the merge. Would be a nicer user experience if the comment was kept there by default (or at least have an option for doing so).
4 votes -
Automatically update workspace when when newer changesets in a branch
When you sync and pull a branch from the repository from the cloud, you have to manually open the Workspace Explorer and then press Update Workspace button to update the files to the newest changeset. Our productivity would improve if the workspace files would be updated immediately upon sync and pull.
3 votes -
Add support for Atlassian Crowd Authentication
And SSO with Crowd in the webUI.
Or at least a way to write our own authentication plugins.3 votes -
Use internal viewer by default instead of "Open file"
The internal source code viewer is used for displaying diffs only. Add an option to always use it instead of the "Open" / "Open with" to open a single file.
Why:
— when browsing a changeset, displaying files that only exist in the source xor destination gives the user a totally different UX than the when a diff is displayed
— when double-clicking on a file in the "browse repository" view, a heavy-weight application such as Visual Studio is launched, instead of a quick and easy text file viewer.In both cases it is slow and impractical.
3 votes -
Add support for namespace in "find branch" command
Currently, finding a branch by namespace is not possible. Even worse, [find branch where name = 'main'] returns 1 branch, but [find branch where name = '/main'] returns none!
Please add full namespace support so we can find branches by complete name, such as [find branch where name = '/main/task001/subtask_1'].
This request originates from the following forum post:
11 votes -
Exclude identical files from Diff (between selected changesets)
When selecting two changesets on two different branches and choosing "Diff selected changesets", the resulting Changeset Diff view can contain identical files (files that do not differ at all between the two changesets). This could happen if the same change has been applied to a file on both branches, without a merge.
In this case I suggest that the identical files be hidden from the Diff view. The whole point of a Diff is to see the files that differ, not the ones that don't.
(NOTE: In my case, I had loads of identical files due to an import from…
24 votes -
Shelve for read-only xlink
It will be useful to have possibility to shelve changes made in "main" repository even if some of files which are changed are located in repository connected by read only xlink. Now shelve is treated in the same way as checkin and it is not allowed to do such operation
1 vote -
Add PLASTIC_REPLICATION_TARGET environment variable to Replication Read triggers
In a distributed development environment (a central server with the 'good' set of source), when you use Replication to Pull a branch you can identify the source repository in the before-replicationwrite trigger from the PLASTICREPLICATIONSOURCE environment variable and the target repository from the PLASTICBRANCH environment variable. In this way you can check that the repositories match and you aren't corrupting your local repository with branches from another repository.
However, when you Push a branch, there is no way for the before -replicationread trigger to check you aren't corrupting the central repository by matching you local repository name…6 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.
27 votes -
Apply bookmarking functionality to Changesets view as well
Extend the Toggle, Goto Next/Prev and Clear Bookmarks functionality from the Branch Explorer to the Changesets view (and possibly the Branches view) as well. The set of bookmarks should be shared between all the views and filtered accordingly...
For this to be really useful we first need to get this other uservoice fixed:
3 votes -
Add more tab-sizes in Diff / Merge Editor Options
Here's a quick one:
In Diff / Merge view, the "Options - Editor Options - Tabs" submenu contains only 2 options: "4 spaces" and "8 spaces".At work, we consistently use 2 spaces. Therefore, please add a third option: "2 spaces". Or simply add all the possible choices from 1-10 or such...
3 votes -
WebUI: Sort list of repositories in alphabetical order, and maybe add sorting/filtering option
http://<server>:7178/webui/repos
The list of repositories is shown in creation order (or perhaps by repository ID)
If you have more than a handful of or repositories, this is a pain, especially since the most used ones are likely to be the more recently created ones, and thus at the bottom of the list.Note that in Plastic GUI the Repositories view, Select workspace dropdown & dialog; and for that matter "Open workspace" dialog lists in alphabetical order. as they should. The web should be the same.
This should be a near-trivial change with immediate benefit. Even better
Changeable order (by clicking…
1 vote -
Have the dashed marker in the Branch Explorer for ANY Pending Changes
Currently the "virtual changeset", marked by a dashed circle around your home, will only appear if you have checked out items. However, if you use the "no-checkout"-workflow, you can have changed items that are not checked out, which are pending changes that prevent you from switching branches and so on.
But the Branch Explorer currently does not show this to you, suggesting that everything is "clean", i.e. you do not have any Pending Changes.IMHO, there is no reason to distinguish between "checked out" and "changed" items here, the Branch Explorer should show the dashed marker if you have either.
3 votes -
Make more views openable by command line flags and Plastic:// URLs
As mentioned in the following links, the changeset / branch Diff view from the Plastic GUI can be automatically opened to show a specified changeset or branch. This can be done either via command line / script or (on Windows) by a URL containing a special "Plastic://" protocol:
http://www.plasticscm.net/index.php?/topic/3061-updated-plastic-urls-to-launch-diff-windows/
http://codicesoftware.blogspot.com/2012/11/plastic-scm-4110372-release-is-out.html
This is very handy for automation etc. However, I'd like to see more views available via command line and URL args - Branch Explorer, 2D History, Items, Annotate etc...
53 votes -
Download folder from repository browser
When using the repository browser on specific changeset/branch, give ability to download a single folder from that view.
1 vote -
home changeset hotkey in branch explorer
It would be nice if there would be a hotkey for going to the home changeset in the branch explorer.
We use this feature very often and after the button was removed from the top bar, it would now be easyer to this with a hotkey instead of the "floating" menu in the branch explorer.
9 votes
- Don't see your idea?