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. Please support 'not like' in cm find query language

    Please can you add support for 'not like' in cm find query language.

    Our example use case is to list all of a developers changes excluding any work in progress (wip).

    find changeset where comment not like '%wip%'

    7 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. High DPI Support for Plastic SCM Visual Studio Extension

    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)
    Close
    Close
    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)
    Close
    Close

  3. Jira integration - make Custom Field ID optional

    In Jira integration settings (I mean Issue trackers settings in Plastic SCM) it is necessary to provide a Custom Field ID. After each checkin Plastic SCM appends a list of modified files to that field in an associated Jira's task. The problem is that it takes extra time after checkin, during which the GUI freezes even for a couple of seconds.

    On the other hand, when you don't provide the field ID, an error message is generated after each checkin.

    Could you please make the field optional, so that when no ID is specified, chekin info is not appended to…

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Branch Explorer: make selection and search results more visible!

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

  5. Preserve changeset comment when closing pending tab or the app

    When you close the pending tab you lose the comments. This can be done by accident or when you close the app.

    It would be great if the comments were preserve rather than lost.

    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…)
    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)
    Close
    Close

  6. Re-open custom branch explorers when restarting GUI

    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)
    Close
    Close
    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)
    Close
    Close

  7. Option - always display branch comment in Branch explorer (not only from issuetracker)

    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)
    Close
    Close
    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)
    Close
    Close

  8. Add "Delete" command to macPlastic

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

  9. Add "Checkin to a new branch" to macPlastic

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

  10. Add "Undo Unchanged Files" to macPlastic

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

  11. Make semanticexcluded.conf file work from wkspace and global config as well

    The semanticexcluded.conf file can be used to control which file extensions are consider for Semantic Diff.

    Currently, this file only has an effect if it's put in %LocalAppData%/plastic4/.

    Just as for the ignored.conf file, for greater flexibility this file should work also when placed in:

    • Workspace (or repository) root.

    • Global config (rep:plastic-global-config, folder <repo>/workspacetree/

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Show author on each entry in "Explore changesets on branch"

    In the "Explore changesets on this branch" view, display also the author of each changeset in the list on the left. (Currently on display is cs-number, date, comment but not whodunnit... ;)

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Add Environment Variable to Edit Review trigger to identify review id

    If a branch has multiple Code Reviews there is no way for the Before and After EditReview trigger to identify which code review is actually being edited. The current environment variables provide the new values and there is no way to determine what the old values were.
    This is important because (for example) we want to only allow certain users from changing the Review Status from Pending to Approved. Therefore we need to find the existing values for the review being edited.

    The suggestion is to add an environment variable (PLASTICREVIEWID) for the review ID being edited.

    30 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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

  16. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. Restore the previous/next item keyboard shortcut in branch diff and code review

    Could you please bring back the previous/next item keyboard shortcuts that used to be available in branch diff and code review? They existed in Plastic SCM 5.4.16.663 (Yaguate), but they are no longer available in later releases. It is no longer that easy to move between files listed in the top pane.

    Now that they are unavailable, there is too much clicking. We can no longer perform code reviews as efficiently as we used to. It really matters when you perform many of them on a daily basis.

    Thank you in advance. We will be grateful.

    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…)
    12 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)
    Close
    Close

  19. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 3 5 … 15 16
  • Don't see your idea?