Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

307 results found

  1. It would be awesome if I could filter the Branch Explorer in the same manner as the Changeset view (simple filter and custom find command). The filtered out changesets will be hidden as they are when using Show only relevant changesets or History of an item as a 2D tree.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. It would be useful if the defined filters had checkboxes to quickly enable/disable them so you can have different settings in different views and some common filters defined.

    This feature doesn't seem to work well with show 'selected branches in a new diagram'. Should inclusions and 'add child/parent branches' only consider branches that would otherwise visible? ie. all in the default explorer, but not add in new ones in the custom one?

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. If we create a new branch and switch to it then the branch appears as empty and the little house icon is not moved to the new branch.

    if we make a merger from another branch then the merge is done to the previous branch.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Jira is one of the most popular issue/task tracking software. Jira 4.2 is supported right now, but version 4.4 (released 2 August, 2011) is not yet supported.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Admin →
  6. There should be user defined views for the Branch-Explorer. Much like the coditional format thing.

    You add some rules (more than one possible) to a view on which branches you want to see in that view. Maybe these views should be serverwide and not bound to a single user.

    In the Branch-Explorer you can select a view and see all branches matching the defined rules for this view.

    This is a extension to you branch visibility system. But with multiple definitions to easily switch between them.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. A major missing feature of Version 4 is the seamless upgrade of a version 3 installation to the new version 4 format.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  8. Currently I use StarTeam revision control but evaluate PlasticScm. The first thing I noticed is that it is not possible to hide files marked with Private/Ignored and Controlled/Hidden changed in the Items view.
    I don't want to see temp, exe-files etc here.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Under "BranchExplorer", introduce a new option under "Display Options" to filter out branches by user name.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. It would be great to have the possibility to just install the plasticscm commandline on Linux systems (e.g. apt-get plastic-cm). This would make it much easier to get this great source code management system more tolerated by old-fashioned GIT fans.

    15 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 →
  11. There are only changeset numbers and base/source/destination titles shown in the Merge Tool (or any external merge tool). It will be very helpful if the names of branches will be shown too. When I merge one branch to another I do not remember (and care about) the changesets numbers and I might be not confident what the source is and what the destination is. The branch names would help me to figure out which version is which immediately.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Selecting a text in Plastic (in Merge tool, diffs, Annotate) is different than in other applications as described here:
    http://www.plasticscm.net/index.php?/topic/1291-some-ux-issues/#entry8989
    Make text selection to be aligned properly, please.

    13 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 →
  14. If the entered data are invalid in a new workspace dialog, then a message box appears (which is good) and the dialog is closed (which is bad). Users want to return to the dialog and fix the item, not to fill it again.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. High DPI support for high resolution/ high DPI workspaces. Than you!

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. This would be very useful for custom integrations. Now, we have to poll regularly to find out, if any attribute of an object has been changed.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. When updating the list of changesets the current selection is lost. I suggest always maintaining the selection state. This is important for persons reviewing the history of a branch or repository respectively. They need to track which changeset they are currently investigating.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. I had a situation where I had an attribute defined for one repository and used it in the branch explorer for custom formatting rules. If I used the Branch Explorer to view any other repository it would crash the GUI. If I then deleted the attribute without removing the formatting rules it would crash the GUI everytime I launched it.

    Full post at http://www.plasticscm.net/index.php?/topic/717-branch-explorer-crashing/

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Before we can use Plastic 4, we need the plugin for our Jenkins CI build server to work.

    12 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 →
  20. At present it will use whatever the OS default is, it would be nice to be able to custimize this within Plastic, e.g. a simple table of file extension versus application (don't forget to allow for files with no extension, e.g. INSTALL, README, etc). This would make life easier fot instances where no defaul is even set (e.g. my Linux VM), and also cases where by default I want to edit files in Plastic but run them in my OS (e.g. script files).

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?