531 results found
-
Display more information in the Repositories view
In the Repositories view, very little information is displayed about the repositories listed: Name, namespace/hierarchy, server. That's all.
When I list my repositories I want to see something similar to the Branches view: Owner, Creation date, Comment
(The Comment field was requested in another uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/8063376-repository-description)
But most importantly, I'd like to see number of branches, number of labels, number of changesets! This info could be displayed in an "extended information" sidebar, also just like in the Branches view.
4 votes -
Possibility to undo checkout without loosing file content changes
Let the user undo a checkout without loosing the modifications themselves. The result would be a file with status "Changed".
Neither the content nor the file's timestamp should change by this operation.
Currently, undoing a checkout always results in downloading the versioned content.13 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 -
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 -
Support for working DVCS with a repo "hierarchy" and easy local repo creation/sync
Definition: when I refer to a repo "hiearchy", I mean some repo ("the top" level repo) and all of the repos xlinked below it (those repos may contain xlinks to repo, thus the "hierarchy").
Today, if you have a large and complex repo hierarchy, it make it very difficult to work distributed.
Use case: A "top" level repo than contains in it's referenced "repo hierarchy" 200-300 other repos via xlink. These other repos may be several levels of xlink deep. The purpose of all of the xlinks is component/reuse structure of coding.
While creating such a repo on a central…
3 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 -
Reuse the "Explain Merge" view for existing changesets
The "Explain Merge" functionality is currently only available while performing a merge, and not in retrospect when looking at an existing changeset containing one or more merges.
I suggest adding this functionality to the "Diff changeset" view as well. it could be activated by context menu on a "Merged from ..." changelist header.
2 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 -
Improve vertical ordering in Branch Explorer, make use of hierarchy
The default ordering of branches in Branch Explorer could be improved. It should respect and make use of the branch hierarchy, so as not to cross lines unnecessarily.
When I have several top-level branches with some child branches each, they are not grouped together vertically in a hierarchically logical order. Instead they seem to be randomly placed (?) leading to a lot of lines crossing each other. (I always enable "Display cross-branch changeset links" which makes this more obvious.)
I think child branches should always be displayed below their immediate parent (or sibling if multiple children overlap in time).
14 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 -
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 -
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 -
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 -
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 :-)
-
Extend "Explore changesets on branch" to new command "Explore history" in Items view
When looking at a branch, we find the "Explore changesets on this branch" window to be very useful, more so than the similar "View changesets on this branch".
In the Items view, the command "View history" is similar to "View changesets on this branch" but it is further filtered to cover only the selected subtree or single file. However, there is no equivalent to the "Explore changesets on this branch" window for the Items view.
I propose adding a context command "Explore history" in the Items view, so that the excellent "Explore" window can be similarly filtered to a subtree…
4 votes -
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 -
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
- Don't see your idea?