General

General

Categories

JUMP TO ANOTHER FORUM

  1. As it is now, to be able to cloak stuff on initial update we need to put a cloaked.conf file in "%LocalAppData%\plastic4\" on my local machine. This file is then applied to all workspaces.

    However, workspace-relative rules (like "/product/install/redist") do not seem to work in this case, they only work in a cloaked.conf put inside the workspace.

    This is inconvenient, since you will then need to apply a less-specific rule (like "redist") to the less-specific target of "all workspaces", running the risk of matching things you did not intend...

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. For integration with issue trackers there is a "Global extension configuration" feature, implemented through a special repository "plastic-global-config". This could be extended as a way to offer server-global configuration of cloaked / ignored items, revision filetypes etc.

    This would be an alternative to adding .conf files for all workspaces locally on each machine, under %LocalAppData%\plastic4.

    (I was told this is already on the roadmap...)

    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  ·  Flag idea as inappropriate…  ·  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. Currently command 'cmd find revision' for changsets which are result of merging does not display files which were included in them.

    This leads to situation that if 'branch per task' approach is applied Jenkins plugin is not able to properly present modified elements in Changes chapter.

    If from any reason 'cm find revision' behaviour shall be preserved than other command shall be used in Jenkins plugin (e.g. "cm diff cs:XY" and the "cm log cs:XY") as suggested on PlasticSCM forum

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Currently, I have to go through one-by-one for directory conflicts and resolve them individually. This is painful when I have 144 evil twin conflicts.

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. i think it is mandatory for all textual input fields.

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow some way to restructure branch parentage. CLI or or other power-user way would suffice...

    If it's true that child branches and top-level branches are identical types and the hierarchy is only for display purposes, I would want to have some way of changing the parentage of a branch (at least from the CLI).

    Make child branch from top-level branch, and vice-versa.

    There may have to be restrictions on this, like "parent can only be set to root or creation point"?

    The practical use-case for us is that we have imported some top-level branches from SVN that logically should be…

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. There is great feature which allows to put automatically time, date or branch name into check-in comment.

    But I have one observation - formating syntax variables are evaluated only ones when Pending Chanegs tab is opened first time.

    If in meantime branch will be switched and refresh button clicked it still remains the same. So it leads to situation when both {1} (Data) and {3} (Branch name) can be complately out of sync with real check-in operation.

    I propose that refresh shall also re-evaluate auto-comment string and update Check-in comment accordingly.

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. To make DVCS easier, allow for a local PC repo to be created during the first sync (or perhaps better during the setup of the sync pair). Default to creating the local repo with the same name as the central repo you are settting up a sync with.
    It seems natural to me, that I be able to have the setting up of a sync for the purpose of DVCS be able to create the local PC repo for me, rather than having to create it first, then setup the sync.

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi! I’m glad to say this have been implemented for some time now. Sorry for not keeping you updated on this!

    Now, while creating a Sync View from the Repositories View (Repositories > Right click on a repository > Create new Sync View (push/pull)), or from the Cloud View (same steps as before), you can create the local or remote repositories with a single click (depending on which of them doesn’t exist).

    For example, let’s suppose that you are browsing your local repositories, and you want to create a sync view using your local repository as the source, and the remote as the destination. If there is no repository in the destination server (your Cloud organization, by default) with the same name as the source one, you can create it with a single click.

    If what you are browsing are the repositories in a remote server, it works the same…

  9. Third party integrations and the ability to make our own plugins is great on Windows, but don't seem to be supported on Mac Plastic. If there was some way to use the same code for both platforms, that would be even better!

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi Eric,

    Thank you for your interest in improving Plastic SCM!

    We’re really happy to say that both GTK Plastic and MacPlastic are fully compatible with existing and custom issue tracker extension libraries. However, the only supported functionality at the moment is the checkin log when working in Task on Branch mode.

    Since the issue tracker extensions are implemented using C# and the .Net framework, you can absolutely use the same libraries available for Windows, even your custom ones!

    Please follow these steps to enable your extension:
    1. Edit your client.conf file (located at ${HOME}/.plastic4/client.conf by default) and add the following lines inside the ClientConfigData tag:

    1.1. You’ll need to set the AssemblyFile attribute value with your own, of course.
    2. If you start MacPlastic right away, your extension won’t work because it lacks the appropriate configuration values. However, the configuration file itself should have been created now. You…

  10. The Plastic SCM Jenkins plugin currently does not process build parameters for the selector text.

    If this was supported, one application of this is would be to parametrize a Jenkins build such that a branch can be selected as a parameter.

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Please add the ability to search for changesets by text in the comment.

    We start the comment for each changeset with the story/issue number that it fixes, but we have a hard time finding them later in the sprint for code reviews. Alternately, a separate, searchable field just for story/issue ID would be equally awesome.

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. In the dialog that pops up to confirm addition of a .ignored rule, make the text box editable so we get a chance to modify it before applying. (For example, we may want to replace part of the workspace-relative path with a ** wildcard.)

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. macPlastic no longer lets you undo unchanged files - which seems to be a huge oversight - even Perforce lets you do that.

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add the "Checkin to new branch" feature to macPlastic. This is already in the windows plastic.

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. macPlastic doesn't let you delete a changes.

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. When an issuetracker extension is active, the branch comments on ticket-branches are auto-populated from the associated ticket titles. Additionally, these branch comments are displayed (next to the branch names) in the Branch Explorer graph.

    This is very convenient, but I think there should be a "Display option" to always "display branch comment", not only for those that are coupled to a ticket and not only when using an issuetracker.

    This new option can be used for additional control over how (ticket and non-ticket) branch names are displayed (similar to the "Display full branch names" option).

    Actually, it would be both…

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. We use the "Branch Explorer - Show selected and related branches in a new diagram" functionality very frequently. It's an awesome way to quickly focus on just the relevant parts of the branch tree. However, when restarting the GUI, all such custom Branch Explorer views are gone! It would be super nice if these custom views would survive a restart...

    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  ·  Flag idea as inappropriate…  ·  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. Please do not use fill-color to indicate the selected changeset/branch and the search results in Branch Explorer! Here's why:

    When using the fantastic feature of changeset and branch coloring (by user / replication-src and by conditional format), it becomes a mess trying to spot the additional altered-color of selection / search-result.

    I have earlier requested a way to change the (changeset / branch) border-color (independently for selection and search-result) into something more different than the current slightly altered gray shade. That would be a start, but I'd prefer to have also an even more eye-catching indication!

    Here are some suggestions:…

    3 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. While the standalone Plastic SCM client on Windows works pretty well on high DPI screens, the Visual Studio extension is awful, not usable.

    Please add support for high DPI, since the Visual Studio extension is generally a very nice thing. Affects all Plastic SCM windows in Visual Studio.

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

    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?