526 results found
-
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 -
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 -
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 -
Visual Studio plugin: Jump to current line when opening Annotate
When opening Annotate from the code editor in Visual Studio, pre-select the annotated line that corresponds to the cursor position in the code editor (and scroll it into view).
7 votes -
Improvements to the Annotate view
Taking some ideas from TortoiseBlame:
When right-clicking a changeset/line, add a choice "Annotate previous changeset" (this is so you can trace the earlier history of the line you're interested in).
When right-clicking a line and choosing "Diff contents of branch/changeset ...", the file that you are currently annotating should be pre-selected in the Comparison window that appears.
Use a tooltip box to display log message (and branch, date etc) when hovering the mouse pointer over a changeset/line.
Remove the horizontal color gradient. While a nice effect, it distracts from the per-date/author color gradient.
Add automatic coloring of changeset text to…
47 votes -
Follow active workspace when showing user in window title
When the preference "Other Options - Show current Plastic SCM user in the window title" is active, it always displays the username configured under "Preferences - General". If there are connection profiles stored under "Preferences - Profiles", this may not be the same user that is logged in at the active workspace. It may not even be a valid user at all, since you will be transparently connected if there is a valid profile.
To be really useful and accurate, the username displayed in the window title should be updated every time the active workspace changes - instead of blindly…
4 votes
- Don't see your idea?