Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

530 results found

  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…

    102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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 repository

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    On 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

  17. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?