Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

307 results found

  1. Merge tool: resolve using complete file (source/base/destination)

    In many cases when I merge branches, an xml documentation file happens to be one that needs user intervention (a manual merge). Because this file is automatically generated by Visual Studio, its content order is random. What's more, it is usually quite large and even several hundred sections in it may need user intervention.

    I don't actually care about the content of that file, because it will be automatically generated correctly when I rebuild the project after merging the branches. So I just click 'Save and exit' without changing anything.

    When I do that, the application asks me an extra…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  2. Bug: Edit changes in Visual Studio Plugin loses changes

    After editing a checkedout file in Visual Studio, open "Diff with previous". The changes can be edited. I found the "Save" button on top (hard to see...), but if you close the window before saving all changes are lost with no warning. I think that is a serious bug.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    9 comments  ·  Admin →

  3. Enable/disable Semantic Diff per file-extension

    Add a way to configure (at least be .conf file) for which file-extensions Semantic Diff will be activated.

    Since release 5.4.16.701 Semantic Diff will revert to text-based diff when it fails to parse a file, but it should be possible to disable it completely for some files (C++ .h headers for example) where the implementation is not yet complete (or simply because the user prefers a standard text-based diff).

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    completed  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

    Implemented a mechanism to disable Semantic Diff for certain file extensions. A semanticexcluded.conf file can be placed inside the Plastic SCM configuration directory: HOMEPATH/AppData/Local/plastic4. This file will contain patterns to match the files to diff. Semantic diff will be disabled for files whose path matches any of those patterns.

    Example: Having the following semanticexcluded.conf file:

    *.h

    /src/core

    The semantic diff won’t be displayed for the following items (server path format):

    /lib/headers/core.h

    /kernel/kernel.h

    /src/core/main.cpp

    /src/core/modules/network.c

  4. Make "Add to ignore list" dialog editable

    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)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  5. Add CLI command to replace existing checkin-comment

    Via GUI it's possible to edit existing checkin-comments and save them.

    In the CLI (cm command line) there is no equivalent to this action. There should be a command to replace the comment of a specified changeset.

    That way we could apply batch pattern-replacement in checkin comments, similar to "git filter-branch --msg-filter". This is not about rewriting history, as only the comments will be modified.

    An example of where this is useful: after import from SVN via Git each changeset has got an appended formatted string, starting with "git-svn-id:" and containing info about the corresponding branch and revision in the…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →

  6. Correct the PLASTIC_REVIEW_STATUS to 'Discarded'. Currently, it is 'Discarted'.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →

  7. maintain selection on update of changeset list

    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)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  8. Provide a setting to disable drag&drop in Pending changes view inside Visual Studio

    I'm using the Visual Studio extension of Plastic SCM. In the "Pending changes in workspace" view dragging and dropping changed files is possible, which opens that file directly in Visual Studio.

    This feature might have been a good idea, but I'm starting to hate it. Every time when I try to select/click on of those files, I move my mouse a few pixels and drag&drop kicks in and opens that file, but my intention was to check/uncheck that file, not opening it.

    Either there should be an option to disable drag&dop, or the sensitivity of the drag&drop operation should be…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →

  9. Gluon / Gluon-like features for Mac

    It would be nice to have some or all of the features of Gluon that are available on Windows also available on Mac. I'm primarily thinking of he ability to download partial repositories to save space by not including certain files.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  10. TeamCity plugin: support agent-side VCS checkout mode

    Currently, the Plastic plugin for TeamCity (Continuous Integration) only supports server-side checkout mode.

    This means the workspace resides on the server and after updating the workspace its contents are copied to the build agent(s). Thus, the agent does not have a complete workspace, only a copy, which means that Plastic commands can not be run in this copy on the agent.

    More specifically, it is not possible to ask questions about the current changeset or workspace status on the agent. (Our build process assumes that the build is done inside a Plastic workspace.)

    Could you please considere supporting the TeamCity…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Admin →

  11. Jenkins selector text should support build parameters

    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)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →

  12. Items view: allow diff of two different files (Diff selected files)

    In the Items view, it would be very useful to select two different files in the tree and compare them against each other.

    As it is, I can't use Plastic's excellent Diff window for this purpose (at least not from inside the Plastic GUI). Instead I have to configure a Diff tool separately with a shell extension and use it from Windows explorer.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    completed  ·  6 comments  ·  Admin →

  13. Put also item revision number on history view

    I would like you to add also additional column in "Item History View" with revision number.

    Currently in "History view" there are changset numbers.
    In "History 2d tree view" there are item revision numbers.
    It is very difficult to connect entries in "History view" with points in "History 2D tree".

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  14. trigger on merge

    In order to be able to implement a condition on merge, such as requiring a peer review before merge, or a test build completing, I would like to see the ability to have a trigger on a merge operation. Today we can trigger on the check-in after starting a merge, but then if the condition is not met we are left with having to undo the merge (remove the pending changes). It would be much easier to implement this sort of "merge gate condition" if the trigger could be on the actual merge operation.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    completed  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

    [New] Release 6.0.16.1471

    Added a new before-merge trigger. This trigger could be used to deny the merge of some branches if certain conditions are not met.

    The trigger can be register using the following command:
    [code]cm maketrigger before-merge merge_gate “/path/to/script” —server=myserver:8084[/code]

    Check the [link] https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide.shtml#Chapter5:Detailedtriggerreference triggers reference[/link] to check all the available info on the merge trigger.

    Remarks: the client and the server should be updated to use this functionality

  15. Allow changing branch parent

    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)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →

  16. Save button in Diff view should have standard Ctrl+S keyboard shortcut

    (I believe this one is already on the roadmap...)

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  17. Search changesets by comment

    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)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  18. When applying a shelve, append shelve comment to pending checkin-comment

    It would be very useful to have the shelve comment transferred to the comment box in the Pending Changes view. Usually the shelve comment is related to the changes made anyway so it makes for a good starting comment. It should be appended, so as not to lose any previously entered comment (that goes for the list of remembered comments, by the way).

    A second-best alternative would be to add the shelve comment to the list of remembered comments...

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  19. spell checker

    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)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →

  20. Workspace-relative paths should work in cloaked.conf when put in LocalAppData

    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)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
1 2 4 6 … 15 16
  • Don't see your idea?