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.

531 results found

  1. Support for more complex find queries

    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)
    Close
    Close
    You have left! (?) (thinking…)
    7 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. file history improvements

    1) highlight the current file revision in the history list GUI & command line as selected by the workspace (I had a feeling it was bold but isn't in 5.0.44.581). If the workspace revision is modified, the parent should still be highlighted.
    2) give an indication of which revisions have been merged in the history list (eg. a column for number of branches seeing this revision; merged yes/no)
    3) populate the 'Properties' panel when selecting items in the 'Version tree' (it is blank regardless of which branch or cs I select, and many of the cs numbers and names on…

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

  3. Icon for files added to source control but not checked in

    Icons in Windows Explorer for files that are currently added to source control but haven't yet been checked in.

    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

  4. Secure code reviews

    Right now there is no mechanism to prevent users from deleting code reviews (unless I've missed something obvious), which is a problem for what we're trying to do. If nothing else it would be nice to have a "before-rmreview" trigger that we can hook into

    14 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. Provide scripts for diff and merge of Open Document Format files (odt, ods and odp)

    Currently there are merge and diff scripts available for xls(x), doc(x) and ppt(x) files, but more and more European organizations are moving to Open Document Format files as their standard.

    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 →
    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. Repository branch templates

    There are many branching scenarios that people use. But it would be nice to have a default template. And template libraries.

    Example when I create a repo I also rename main to Production and create Test and Development branches.

    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. Optimize Annotate

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

  8. Finding changesets / reviews by name with wildcards (where like '%...')

    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)
    Close
    Close
    You have left! (?) (thinking…)
    4 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. flag changesets that won't be merged

    It would be useful to be able to set a flag on a changset such that it won't be merged from the branch it exists on (by merging from a subsequent changeset, although cherry picking it could possibly be an exception).

    I sometimes need to make temporary changes on a branch (eg. for testing), but don't want to risk these getting merged upstream.

    Normally I do periodic checkins of all changed files, so need to be careful to exclude these. It would be nice for the temporary changes to be managed by the SCM in a safe way.

    I don't…

    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

  10. Cherry pick single lines

    Scenario: You're developing a big extension within a dedicated branch. You have a lot of files and changes checked-in with only a few changesets. Now, you need a small portion of all these changes in another branch. You can't use the traditional cherry pick, because you've check-in a lot "unwanted" files with your changesets. Also you changed bigger files which contain needed and unwanted changes.

    Righ now there is no way to cherry pick only some changes from specific files within a branch.

    It would be a great feature, if you could generate a new changeset with only a selected…

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

  11. Add menu item to context menu in branch explorer to fast hide branches

    It would be nice to have an option in the branch context menu in the Branch Explorer view to hide a branch faster.

    If I want to hide a newly created branch that I don't want to see, I have to switch to visibility mode first, search the same branch again and double click it. This could be fastened up by adding a 'Hide branch' option to the context menu of all branches in the Branch Explorer view.

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

  12. automated replication

    I'm working on a main computer and a laptop for when i'm on the road.
    When i'm working on my laptop I would like to have it automatically push changes to my other computer or the central server when I check-in a change-set.

    Also i would like to be able to subscribe to a repo of specific branches so it automatically pulls changesets from the central server or the computer.

    14 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. Server authentication configuration in LDAP mode should allow for LDAP queries

    Support for LDAP queries (including OR operator) that would allow better specificity in configuring access control to repo server.

    Screenshot of config wizard: http://screencast.com/t/uXZVgpUvV

    2 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

  14. list changeset creation date in items view

    The date column of the items tree is the local modified time of the file in my workspace. It would be much more useful to list the time the changeset that contains it was created. eg. how do I find the most recently modified files in a directory? Similarly a 'cm ls -lrt' equivalent would be useful.

    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…)
    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. show changeset comments when comparing files

    The diff tool lists the changesets being compared at the top. The tooltip for this text is the same as the text itself, it would be more useful if the tooltip included the comment.

    This would be particularly useful when working with xlinks and the changeset numbers here and in history don't correspond to those in branch explorer (different repos).

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

  16. Workspace-wide exclusive checkout

    Consider the following branches:
    1(root)
    1-1 (branch from 1)
    1-2 (another branch from 1)

    Currently, you can checkout and check-in the file on branch 1-1 and you can also do it on branch 1-2, as long as both checkouts are in their own branch head changeset and not at the same time.

    So when branches 1-1 and 1-2 merges back into the root branch 1, you get a conflict.

    The idea is to have types of files that cannot be merged, never, completely exclusive for all branches, the same way it is done in lock.conf for a per-branch basis.

    65 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…)
    15 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. prevent merge to workspace containing changed items

    Usually I would not like to group changes from a merge (rebase) with those from editing files (development). I would like to be prevented from making this mistake and checking it in before realising.

    There is already a similar option when switching/updating the workspace: "Do not allow, show an error". Could it be extended to cover merges, or a new option added?

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

  18. improvements searching for changesets in branch explorer

    If you search for a changeset and it is not found, nothing happens. There could be several reasons:
    1) the changeset does not exist
    2) it is hidden due to 'display only relevant changesets'
    3) it is a recent addition and you need to refresh the view first

    It would be helpful if a dialog was shown with the reason, with perhaps an option to do either 2) or 3) and then find it.

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

  19. list changed files in branch explorer properties

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

  20. TeamCity Plugin Customizable Workspace Name

    Is it possible to specify the name of the workspace that is created for a build configuration when using Plastic 5.x with TeamCity 8.x? Currently a workspace is dynamically created with the name tc### where the number actually correlates to the primary key of the vcsroot_instance stored in the TeamCity configuration. What this means is that every time we update the parameter for the build configuration that contains the name of the Plastic branch we wish to use, Plastic tries to create a new workspace. This is a problem because the same folder is being used and already…

    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…)
    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
1 2 … 20 22 24 25 26 27
  • Don't see your idea?