535 results found
-
conditional format/in-/exclusion rules based on repository
Right now I have no way to define custom rules for only one repository.
Also it is not possible to identify the repository within the rules condition.Workaround: add a attribute to each branch containing the repository name. (Very very nasty)
It would be nice to:
1) have a repostoryName variable within conditions
2) have custom rules for only one repository9 votes -
MergeTo operation shall support --mergetype and -c/-commentsfile
It looks that currently MergeTo operation is ignoring --mergetype parameter. If only automatic merge of changes from both source and destination is possible Plastic is doing it.
It would be good to have a chance to explicitly show that changes only on one side are allowed and exit with failure if there are some also at the other.
Additionaly for now it is not possible to give comment which will be used for check-in operation after successful mergeTo.
6 votesOn the release 7.0.16.2077, we added the new server-side merge that extends the existing merge-to functionality.
Using the server-side merge, the file conflicts can be resolved and the merge resolution options (—mergetype, —keepsource & —keepdestination) are supported.
The server-side merge is still on preview so you need to enable it adding the following setting on the client.conf. Check how to do it on the release notes: https://www.plasticscm.com/download/releasenotes/7.0.16.2077
Remarks, the server and client version must be equal or newer than 7.0.16.2077 to use the server-side merge.
We comment option will be documented soon, we already plan a task to do it in the next few weeks. Sorry for the delay.
Best regards
Borja
-
Make Diff listen to file-change-notifications and ask to reload
The Diff view/window in Plastic does not listen to filesystem notifications about file-changes when diffing a file in a workspace.
It should discover external changes to the workspace file and ask to reload/recalculate the diff when needed. Other Diff tools I have tried do this...
6 votes -
Show Home changeset whenever possible
I would like the "Home" changeset to always be shown (when at all possible) in all the branch-explorer/2D-revtree views. This would make it easier to relate the view to the current workspace contents.
In all those views, I'd like the Home changeset to be displayed regardless of date filter (possibly with a dotted parent-changeset arrow to connect it with the nearest date-filter-included changeset).
In the 2D revtree I simply want an extra U = Unchanged changeset (on the relevant branch) with the Home icon above it, in the cases where the home changeset/branch would not otherwise be included.
NOTE: Exclusion…
3 votes -
Add "Switch workspace to this branch" to context menu for changeset
Switching to a changeset is something you rarely do, compared to switching to a branch which is a very common operation. It would therefore be very convenient to have the latter command available even when a changeset is selected (in the Branch Explorer).
When switching to a changeset, the workspace is pinned to that changeset and can not be updated. This was confusing for us when we had just migrated to Plastic, and we still have users doing the mistake of switching to a changeset instead of a branch. I think having both variants of the Switch command available when…
7 votes -
Change the wizards and profile creation to allow working mode and credentials to be changed/overridden
You used to be able to specify the working mode and credentials (username & password) when configuring the client and creating profiles. Now, if the server is set to ADWorkingMode it forces the client to also use ADWorkingMode and forces th userid & password to the local domains credentials. This makes connecting to plastic server from remote locations problematic and rather difficult to achieve. If you could still simply change the client to LDAPWorkingMode and profile username/password it would be much easier to accomplish this.
6 votes -
Add "Open" and "Save this revision as" in 2D (File) History as well
In the Items view, for a single file we have the (customizable) submenu "Open".
In the History list for a single file, we have the "Save this revision as..." command along with "Open" and "Open with...".
For consistency and ease-of-use, the "Open" submenu should be available in the 2D History view for a single file as well. Also, the "Save this revision as..." command should be added to this "Open" submenu.
This is much related to another uservoice that requests adding the "Save this revision as..." command to the "Open" submenu in the Items view as well:
3 votes -
VS plugin: Add in-editor diff markers with associated commands
We were using the VisualSVN plugin for Visual Studio before, and we miss the excellent "Quick Diff" feature: https://www.visualsvn.com/visualsvn/features/
This feature replaces/enhances the "Track Changes" markers in the Visual Studio code editor with colored lines (in the left margin), to indicate blocks of lines that are changed relative to the latest changeset (different colors for modified, added, deleted). It also adds commands (revert block, navigate prev/next change block).
There are some other (open source) plugins that offer similar functionality: "Git Diff Margin", "TfsPendingChangesMargin", "HgVS".
12 votes -
Allow setting a color for each label, changeset and branch
It would be a nice feature to allow setting a color for elements.
Examples:
- set the label color red to mark it as "important".
- set the branch color to green to indicate that the branch is the "test branch"46 votes -
option to select diff tool on the command line
If you use a console based diff tool such as vimdiff it can cause the GUI problems. It would be nice to be able to set different difftool preferences for the GUI and 'cm diff', possibly with a command line option:
cm diff --tool=vimdiff
It might be necessary to give tools names or id's in the GUI preferences to reference from the command line so you can easily configure the arguments.
9 votes -
Add button "Set as default workspace path" in New Workspace dialog
This is a new idea inspired by another uservoice that was declined:
https://plasticscm.uservoice.com/forums/15467-general/suggestions/10300338-remember-last-entered-path-for-workspaceHowever, the solution suggested here supports all three of the conflicting scenarios given by Codice staff when declining the earlier uservoice: a proposed initial default path (set on first install), a configurable root path (now set from GUI) and a way to remember the last entered path (but only on demand).
There is a setting DefaultWorkspaceRoot in file guiclient.conf, but there is no way to set that from the GUI. I propose adding a link/button "Set as default path for new workspaces" or similar in the New…
3 votes -
Horizontal comparison panes in diff viewer
Would you consider adding optional horizontal comparison panes to the diff viewer, displayed or hidden with a button or a key combination?
It becomes useful when there are changes in long lines. Thanks to them you don't usually have to scroll the window in order to see all changed areas. This idea comes from WinMerge, which has both vertical and horizontal comparison panes.
3 votes -
Pull Requests
Provide a mechanism to approve merges into specific branches.
One option is to use pull requests with an approval mechanism (of one or more required approvals).This will allow trace-ability and enforcement of organization rules.
Linking it to code review will make it even greater.(Check out Stash for examples)
18 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 :-)
-
Issue tracker: add WebUI hyperlink to ticket when creating branch
We are missing a two-way coupling between Plastic and the issue tracker (in our case Trac). If we have setup a Plastic WebUI, it would be nice if the Plastic issue tracker extension could add a WebUI hyperlink to the ticket comments when we create a branch from a ticket.
This should be doable for Trac at least, since the extension already adds a comment to the ticket when "Mark as open in issue tracker" is checked during branch creation?
5 votes -
Implement a simple popup editor for designing "cm find" queries
This would be very useful for learning and experimenting with the query syntax, and for quickly adding/adjusting a query without having to remember syntax.
It should be possible to build the query by selecting the different targets etc and adding/removing/editing filter specifications. The resulting query text should be displayed.
5 votes -
Indicate date-truncated branch in Branch Explorer
Display a "+" or similar at left/right end of branch in Branch Explorer, when it has been truncated by the date-filter.
5 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 -
Items view: allow Diff of Private files as well
In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This currently only works for two Controlled files or two Controlled folders.
It would be great to have this work for two Private files (or one Controlled and one Private file) as well. You would have to do some detection of txt/bin filetype on the Private files.
3 votes -
Bug: Revision type change is stored on server but not updated on clients
User A changes revision type of an item from binary to text. User B runs update and refresh of items list, but item remains binary. Pressing CTRL+D shows a dialog that quotes "Error: Differences between items of diffente types cannot be calculated". That implies that the change of User A was sent to the server and applied to the item, but the information is not propagated to the other users.
1 vote
- Don't see your idea?