535 results found
-
User Translation Table in Sync View
I wanted to replicate a whole repository and need to map user names.
I managed to replicate single branches using the user translation table. However, in "Sync replication", there is no such option. That is, I have to replicate each branch one by one. I have to select the translation mode in the GUI each time I replicate a new branch.3 votes -
Add option to always show active branch
When using inclusion/exclusion filter-rules in Branch Explorer, the active branch may become hidden. I want some way to force the active branch to be always visible.
There is a special coloring-rule (currentselectorbranch) for the "Active branch in this workspace", but there is no way to do the same in an inclusion rule. (As I don't think it's possible to locate the active branch via a simple find-branch-query?)
I propose adding a way to (optionally) always show the active branch. This could implemented simply as a new "Display option" - "Always show active branch" or as a special inclusion…
3 votes -
Optionally affect xlinked repos when doing "Apply label to workspace contents"
When applying a new label, there is a checkbox "Label all XLinked repositories".
However, when moving a label ("Apply label to workspace contents") there is currently no way to automatically apply (or move if existing) a label by the same name in xlinked repositories.
It would be very nice to be able to do this (as an option).
3 votes -
Improve integration with JIRA
Develop a JIRA plugin for Jira, to improve visibility.
Add options to create branches from JIRA and issues from PlasticSCM.
Embed links to open each other Web Portal.In general, a text box in the Jira issue is not enough. The interaction should be smooth.
69 votes -
Add prio order for inclusion and exclusion rules as well
In Branch Explorer, it's hard to combine inclusion and exclusion rules since there is no way to adjust priority order between them, and exclusion always seems to override inclusion.
I would suggest evaluating (for each branch) the inc/exc rules from top to bottom and stopping at the first (enabled) matching rule (just as for the custom coloring rules). Then you could re-use the "move up" button for adjusting these prios (only keeping the separation of color-rules from the inc/exc rules).
3 votes -
Add a view and a command for viewing all xlinks in a repo
I want to quickly list all the xlinks in a workspace, both in the GUI and on the command line.
The "cm xlink" command lists info about one specified xlink, but how do I list them recursively (without doing a "cm ls -R | grep xlink" or using "cm fileinfo" in every subfolder)?
I think there should be a command for this, perhaps "cm findxlinks", similar to "cm findprivate". A raw list of absolute paths to xlink-folders would do fine.
Also, I would like a GUI view listing all the xlinks in a repo (similar to the Branches view).
3 votes -
Improve the conditional format to support to coloring of branches with un-replicated change sets
I want it to be possible to color branches that have change sets that have not been pushed to some other server via sync replication.
To be specific and explain the background:
I use jenkins to do some builds of my project when the main branch has been pushed to a central repository.
it has happened to me several times that I checked in code (locally) and executed the jenkins project just to discover that it ran old code because my main was not replicated to the main server.I would be happy if my main branch would show with…
6 votes -
Enable namespaced Labels, display as a tree view
Just a simple (crazy?) idea. This would be very nice to have when the number of labels in a repo grows large. A hierarchical Labels view would be consistent with the rest of the Plastic UI.
Implement "soft" namespacing for labels (i.e "Namespaced Labels/Label 1"), similar to the one for branches.
Then add buttons "List view" and "Tree view" to the Labels view, just like the Branches view.
Technical:
No change is needed to how label names are stored, but the forward-slash character needs to be allowed in a Label name (it isn't currently, which is great since it means…3 votes -
Customizable columns
Make possible to select visible columns in table views such as Changesets, Items, Branches, etc.
We want to see Attributes and Labels in a Changesets view, but we usually do not care about GUIDs.142 votes -
Enable re-merging
A feature to enable the user to edit/re-merge a pending merge is something that would improve flexibility and greatly assist new users to the system.
If you accidentally do something wrong in the merge, or change your mind and want to do something differently, it would be great to "redo" either file or the entire merge, and let you change e.g. from workspace to source contributor, or go over a merge of some code without having to undo. Now, after you've done a merge you reach a point of no return.
1 vote -
option to cancel workspace update
A workspace update can be quite slow, particularly if you made a mistake in cloaked.conf. Rather than killing the process, it would be nice to be able to cancel the update.
22 votes -
Add "unrelated merge" indicator in 2D history and filtered branch explorer
When viewing changeset history I tend to think about changesets in terms like "that is the checkin where I merged/rebased from /other_branch". That kind of context is sometimes lost in the Plastic views:
In 2D History if a merge is unrelated to the selected item then the merge arrow is not displayed.
In Branch Explorer if the /other_branch is hidden by filter, the merge arrow is not displayed.
Not displaying the merge arrow in these cases is logical since the /other_branch is unrelated or hidden. However, I'd find it helpful to have some kind of (optional) visual indicator that an…
3 votes -
If a changeset is deleted, switch to the parent changeset and KEEP the changes in the "pending changes"
When a changeset is removed the workspace is switching to the parent changeset and all changes get lost.
I think it is better to keep all changes in the "pending changes", so you do not lose any changes and you can add some more changes.It often happens to me that I forget some small changes, so I have to check in again producing a lot of unnecessary changesets.
87 votes -
Add default filter in Changeset Diff opened from (2D) History
This suggestion is a simple and minimal solution to a feature that is missing in Plastic and that we used a lot in TortoiseSVN - the ability to filter a Changeset Diff to the subtree-path that we're viewing the History of.
I have earlier suggested more elaborate changes to support this feature, but the simplest possible fix for this is as follows:
When opening a Changeset Diff from a (2D) History view of a directory (subtree), automatically populate the "Filter:" box (for the Changeset Diff) with the workspace path of the directory that the History view is working against. (This…
3 votes -
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 -
Search in Branch Explorer should include Branch Comments
The filter box in the Branches view gets hits on words in the branch comments, but the Search box in Branch Explorer does not.
6 votes -
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 -
Possibility to merge independently added files/directories
Two folders (or files) with the same name added into different branches independently, cannot be merged in Plastic now.
It would be priceless in some cases (especially for folders).
http://www.plasticscm.net/index.php?/topic/1224-evil-twin-conflict-resolution/
http://www.plasticscm.net/index.php?/topic/391-directory-merge-fail/175 votes -
Show current changeset in "selector bar" (below workspace tab)
When starting the Plastic GUI (on Windows), the tab for the active workspace tab is selected. Below that is a "selector bar" indicating what's currently loaded (switched to) in this workspace.
If the workspace is switched to a Branch/Label, there is no immediate way to find out which changeset number is actually loaded right now.
Example: When switched to a branch, if the workspace has not been Updated recently we may not be at the latest changeset on that branch.
I propose displaying the actually loaded changeset number in this "selector bar", to have this crucial information readily available regardless…
3 votes -
Lock a Branch
LOCK a branch so no one can perform a merge or checkin except the one who took the lock.
Current scenario: Two or more developers are are working on child branches and want to merge back to the parent branch, if both initiate the merge, the first will succeed but the second will have to re-merge again. To avoid this, the developers can send an email, asking all to wait until he finishes the merge...
Proposed solution: Allow the one to take a lock on the target branch, do the work, and release it. During the lock, others should be…99 votes
- Don't see your idea?