General

General

Categories

JUMP TO ANOTHER FORUM

  1. Annotate for bigger files with long history is very slow and even stops with error. A performance optimization would be much appreciated. Annotation of just a part of a file (https://plasticscm.uservoice.com/forums/15467-general/suggestions/3533001-annotate-this-line) is one option, some caching is maybe another way, how to deal with that.

    48 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  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. The History view and History as 2D tree view do not contain merges affecting the item and do not show any reverts. Therefore those views are not really a history, but only a list of different variants of the item existing in the history.
    See comments for a deeper explanation.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. This would save us a TON of pain working in game dev. Not only make the locks across all branches where the locked files exist, but also setup plastic so you can do multiple commits while keeping the lock.

    45 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. With v1.11.0 they've just publicly released the SCM API (https://code.visualstudio.com/docs/extensionAPI/api-scm), so it'd be greate to have Plastic integrated in this wonderful editor.

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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"

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for VCS PlasticSCM under vcs roots and possibly Webstorms internal changelist, auto checkin and checkout support for editing files. Could be adapted easily from existing IntelliJ plugin to support Webstorm and PHPStorm?

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Please, add the possibility to use queries like this:
    find changesets where branch like 'release%' (to find changesets from branches release1, release2, releaseB,...) or this: find reviews where title like '%fail%' and so on.

    This feature is already available for changeset->comment, but not for changeset->branch or review->title.

    39 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Imagine the following scenario:

    A repo with a XLink with a main branch and a child branch. Both branches have the same XLink.

    Now the following occurs:

    1) XLink is changed in both main branch and child branch
    2) You do a merge from main to child branch

    You'll get a conflict (which is expected). However, the "Source" and "Destination" values aren't very human readable in the GUI. I'm assuming they're the GUID's of the changeset or something similar.

    Could you make it more human readable? Displaying the associated changeset, branch etc?

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. In "Changesets" tab it is possible to right click on a changeset and select "Label this changeset"
    However nowhere in this view can I see if there is a label against a changeset- there are columns for Changeset's Name, Comment, Date , branch et al but not even the "Show Extended Information" shows anything about labels.

    Why this would be useful:
    In my typical workflow I make changes as development proceeds with comments stating what & why things have been done; often with references to issue#s . For example "Fix issue#5341 the conblogminator was crashing with error E54 when the…

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Specifically, I want to find all changesets with two attributes with specific values. Something like:
    find changesets where attribute = 'Review status' is 'none' and attribute = 'Reviewer' is 'somebody'

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. (this is different to the existing idea 'Add git like staging').

    A thing I do in git all the time is use git-gui to select individual blocks and lines to stage and commit. For example I might fix two separate issues in the same file at the same time but want these committed separately.

    Plastic currently only allows committing the whole of a file at a time but I would find the git-like behaviour VERY useful.

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. The tree view in Pending Changes gives a much better overview/visual structure to the things that were modified. However, per default everything is always collapsed. So for each new change one needs to click-open every single hierarchy level by hand, to reach the assets that were actually changed...

    All other tree views (Items, Branches, ...) are affected similarly, and would greatly benefit from such a hotkey.

    I suggest to use Alt-click, as for example, Unity uses that same method to selectively and recursively collapse/open subtrees. 

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. When doing a merge that involves a change in a cloaked file (only in the incoming change) the changes are downloaded when resolving conflicts .

    Please add an option to not even show cloaked files coming in from merges or at least to not download them.

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Currently, when Plastic sees a local file older than the one on the repo, it will be impossible to checkin. Moreover, it will tell you only for the first file it finds, so you have to try checkin again and fix each file individually as long as the error pops up.

    Solution : Show a list of all the conflicts, and for each file (why not also have a button to process all..), let the user choose which file he wants to keep.
    - Keep local file : checkin the local file ; overriding plastic warning.
    - Keep repo file…

    35 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  ·  Flag idea as inappropriate…  ·  Admin →
  16. It would be nice if there were a list of changed files for the selected changeset in the properties tab of branch explorer. This would be much quicker and more convenient than doing a diff changeset and facilitate general browsing. As panel width is limited, maybe only show the filename or put an elipsis at the start of the file path. There should be a context menu to diff the file.

    35 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  ·  Flag idea as inappropriate…  ·  Admin →
  17. Currently local changes to comments and or labels do not register as changes, and thus are unable to be synced outside of the initial commenting or labeling.

    There have been many times I required a developer to add more details to their initial comments, and or had to fix a bad label, and had to change it in multiple places rather than in just one followed by telling everyone to sync.

    I feel this is a very worth while feature to include; as that meta-data is what effectively describes a change-set and right now any changes to those items requires…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. "Shelve pending changes..." is currently not available for cloud server. I'd already be happy if I could shelve them locally, even though I'm working on a cloud server.

    34 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  ·  Flag idea as inappropriate…  ·  Admin →
  19. and make the button, which opens this window more noticeable (both in History and Changesets view), by adding a text label at least.

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Currently Plastic allows Code Review Per Branch. Problem is it shows differences between the original node from which the feature branch was created (in dev) and the head node of the feature branch.
    However, this is a problem: when you update your feature branch merging updates other devs have merged in dev branch.
    Why? Because all their changes also appear in the code review. So at this point is not possible to do a reasonable code review of the code in the feature branch.
    The solution: Take the same approach that BitBucket takes. The code review should show only differences…

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?