531 results found

1. Visual Studio plugin: Jump to current line when opening Annotate

   When opening Annotate from the code editor in Visual Studio, pre-select the annotated line that corresponds to the cursor position in the code editor (and scroll it into view).

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add "Switch workspace to this branch" to context menu for changeset

   Switching to a changeset is something you rarely do, compared to switching to a branch which is a very common operation. It would therefore be very convenient to have the latter command available even when a changeset is selected (in the Branch Explorer).

   When switching to a changeset, the workspace is pinned to that changeset and can not be updated. This was confusing for us when we had just migrated to Plastic, and we still have users doing the mistake of switching to a changeset instead of a branch. I think having both variants of the Switch command available when a changeset is selected would help beginners understand the distinction. For experienced users it would still be a nice shortcut.

   Switching to a changeset is something you rarely do, compared to switching to a branch which is a very common operation. It would therefore be very convenient to have the latter command available even when a changeset is selected (in the Branch Explorer).

   When switching to a changeset, the workspace is pinned to that changeset and can not be updated. This was confusing for us when we had just migrated to Plastic, and we still have users doing the mistake of switching to a changeset instead of a branch. I think having both variants of the Switch command available when… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Show the current branch in Workspaces overview

   Currently, in the Workspaces overview, you only have columns for "Name", "Path" and "Repository". It would be nice to have another column "Current Branch".

   This would make it easier to identify the correct workspace for a certain branch when having multiple workspaces with varying branches.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Shrink height of branches displayed in Branch Explorer view

   I would like the branch graphics in the Branch Explorer to be shrunk but keep the text the same size.

   I use the Branch explorer all the time. I need to be able to read the branch labels and date headers, but at the same time be able to see a decent amount of history.

   Press (-) button until display stops changing. Then press (+) button twice. Graphics size at this level is good, but the text is unreadable. Press the (+) button one more time. Now the text is readable but the graphics are spread apart too far.

   I just upgraded 4.0 to 4.5; 4.0 was a little better in this regard.

   I would like the branch graphics in the Branch Explorer to be shrunk but keep the text the same size.

   I use the Branch explorer all the time. I need to be able to read the branch labels and date headers, but at the same time be able to see a decent amount of history.

   Press (-) button until display stops changing. Then press (+) button twice. Graphics size at this level is good, but the text is unreadable. Press the (+) button one more time. Now the text is readable but the graphics are spread apart too far.

   I… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Improve "Cherry pick from changeset interval" range

   The "Cherry pick from changeset interval" is a bit confusing to me.

   For example:
   I want to cherry pick from changesets cs10 to cs15.
   So, I intuitively select cs10 and cs15 and do a cherry pick interval merge. But then, I notice, that there is no cs10 involved. The merge begins at cs11 and not cs10.
   So, when I want cs10 included, I have to select cs9. But that is very unintuitive to me.

   It get's even worse, when I click on the merge arrow afterwards and it shows me "Changeset interval (9 - 15)".
   That's wrong, because there is no changeset 9 integrated. It's cs10 to cs15 involved.

   So, maybe, it's a philosophical problem about how you start counting or look at intervals. But for me, it's totally logical to select these changesets, which are also part of a merge. So, when I see "interval cs10 to cs15", I naturally think cs10 is involved and part of the merge. I would not think, that cs10 is only a boundary and not involved in that merge.

   Could you fix this please or make it optional for the users, how the interval should be interpreted? (Maybe there are others around, who may have no problem with the current interpretation.)

   The "Cherry pick from changeset interval" is a bit confusing to me.

   For example:
   I want to cherry pick from changesets cs10 to cs15.
   So, I intuitively select cs10 and cs15 and do a cherry pick interval merge. But then, I notice, that there is no cs10 involved. The merge begins at cs11 and not cs10.
   So, when I want cs10 included, I have to select cs9. But that is very unintuitive to me.

   It get's even worse, when I click on the merge arrow afterwards and it shows me "Changeset interval (9 - 15)".
   That's wrong, because there is… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Possibility to choose jira task from checkin

   When "Checkin changes to different branch" it would be nice if you could explore all jira task, instead of having to type the correct name.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Add Custom 'Open With' options to Gluon

   It would be great to be able to get the custom Open With functionality from Plastic GUI over to Gluon. The ability to be able to define custom 'Open With' targets would be indispensable for our work.

   For example, Autodesk Maya's versions are frustratingly difficult to configure with Windows 10 (only one option appears in the Default Apps settings), and this configures ALL Maya files to open with that one version.
   We require the ability to be flexible and open files with different versions of Maya for different projects (based on when that project kicked off, therefore maintaining project compatibility).
   It'd be amazing if the Custom 'Open With' options were available within Gluon for our artists, or the ability to set those options within the Plastic GUI and have it carry over to the Gluon interface.

   It would be great to be able to get the custom Open With functionality from Plastic GUI over to Gluon. The ability to be able to define custom 'Open With' targets would be indispensable for our work.

   For example, Autodesk Maya's versions are frustratingly difficult to configure with Windows 10 (only one option appears in the Default Apps settings), and this configures ALL Maya files to open with that one version.
   We require the ability to be flexible and open files with different versions of Maya for different projects (based on when that project kicked off, therefore maintaining project compatibility).… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Japanese

   Add localization support to Plastic SCM / Documentation for Japanese, Chinese and Korean.

   If possible, also translate your website into the above mentioned languages.

   Game dev companies in Asia use Perforce. If you translate your product and site, they may see a reason to switch.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Support displaying deleted files in "Explore workspace" (Gluon)

   I'd like to be able to have the option to display deleted files in the "Explore workspace" tab in Gluon.

   This would greatly simplify viewing the changeset history of deleted files by supporting the same details panel workflow that is currently used for non-deleted files.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Show file checkout state in client without trying to checkout

    Right now if one user performs a checkout on a file there is no way for other users to see that without attempting to checkout the same file.

    This primarily matters for files set to exclusive checkout, as files are not locked from local changes. If each file's checkout state was visible in the client automatically, fewer mistakes would occur where changes need to be undone or moved to a new file

    The attached photo is the only feedback from the client on file checkout state currently

    •  

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Automatically update folder contents when updating an xlink in a workspace

    (The following text is specifically about read-only xlinks. I am not sure if it applies to writable xlinks as wel.)

    When I use Plastic, I expect that the contents of an xlinked folder in my workspace is updated at the same time that the xlink itself is updated. Plastic currently requires me to perform a workspace update to download the changes. Me - and everyone else on my team - find this behaviour counterintuitive. I would like to see the following changes in behaviour:

    1. When I create or modify an xlink, I would like that Plastic update the xlinked folder contents immediately, rather than require me to create/modify the xlink locally, check it in, and then update the workspace.

    2. When I receive an xlink modification as part of merging from another branch to my current branch, I would like that Plastic update the xlinked folder contents immediately, instead of waiting for me to click "Update Workspace".

    Reason for change 1: The need to check in the xlink before receiving the new files locally makes it impossible for me to verify the consistency of parent repository + xlinked repo together before checking in.

    Reason for change 2: The need to click "Update Workspace" to update the xlinked folder contents means that the "merge from branch X" operation in the UI does not actually guarantee that my workspace includes the changes from the other branch; merge + update is necessary, but only in situations where xlink changes are part of the merge.

    Change 2 also means that I can freely choose how I introduce or modify a new code module that most of the team wants to maintain as a separate entity: either by duplicating the code module's files into the current repository, or by xlinking to another repository containing the module. Without change 2, there is a hidden cost to using an xlink: Everyone else on the team that has a work branch in flight will need to click "Update Workspace" after they have merged my in my changes to a work branch, or else it will appear to them that some source files are missing / out-of-date related to my changes. They do not care that I happened to use an xlink, they just expect that after a merge, their workspace is up-to-date (like it is in 99% of cases when merges do not include any xlink changes).

    (The following text is specifically about read-only xlinks. I am not sure if it applies to writable xlinks as wel.)

    When I use Plastic, I expect that the contents of an xlinked folder in my workspace is updated at the same time that the xlink itself is updated. Plastic currently requires me to perform a workspace update to download the changes. Me - and everyone else on my team - find this behaviour counterintuitive. I would like to see the following changes in behaviour:

    1. When I create or modify an xlink, I would like that Plastic update the xlinked folder… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Visually indicate, in Code Reviews, reviews that have been merged into main

    It's easy to forget to merge a branch after a code-review is completed.
    Change the colour-coding:
    - Blue: Review requested
    - Red: Rework requested
    - Yellow: Reviewed
    - Green: Merged

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Make customextensions.conf available from global config

    The customextensions.conf can only be configured clientside while such extensions are often to be applied accross entire teams/companies.
    Making it available trough the global config would take away the burden of manually updating each users client file.

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Ability to select default branch

    We'd like to be able to set a default branch without setting up triggers.

    The main purpose would be to have all users default to a specific branch, so that inexperienced users don't have to manually select it. We realized this can be done through an after-mkworkspace trigger, but this would not solve the other issue (below).

    For our use case, we do not have any files in /main so when looking at the repositories, it says the repository is empty which is not accurate. /main is empty, however we have other branches with data. This could be confusing for users trying to setup their workspace for the first time.

    We'd like to be able to set a default branch without setting up triggers.

    The main purpose would be to have all users default to a specific branch, so that inexperienced users don't have to manually select it. We realized this can be done through an after-mkworkspace trigger, but this would not solve the other issue (below).

    For our use case, we do not have any files in /main so when looking at the repositories, it says the repository is empty which is not accurate. /main is empty, however we have other branches with data. This could be confusing for… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Add Image List to the workspace tab control

    Add Image List to the workspace tab control using the images from the actions to indicate the function.

    On Branch Explorer tabs then show just the repo information text vs "Branch Explorer for repository..."

    Given Xlinks in a project I may have 3 or 4 Branch Explorers open at a time and the tabs all say "Branch Exporer f..."

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Make the listlocks command use lock.conf configuration

    Currently, the listlocks command doesn't use what's configured in the lock.conf, making it confusing when using an external lock server. See this thread for more info : http://www.plasticscm.net/index.php?/topic/2064-exclusive-checkout-in-dvcs-configuration/#entry13367.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Hability to query file contents (grep-like)

    It would be nice to be able to search database files for their contents, and accross history.

    I am picturing a use case where a user would like to download the last changeset before a particular piece of source code was deleted, for instance. The user could search the repository for files containing that particular text, and the server would return the file names, and perhaps the first and last changesets where the text still appeared in the file.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Automatic comments based on semantic changes

    I would love the ability to select a new button "auto comment" from Checkin Comments drop-down on the Checkin UI that would use the the semantic code engine to generate comment lines like the following:

    -added update methods to InquiryRepository
    -added Username parameter to SetReferralDelivered() in ReferralService
    -deleted class MyFakeClass
    -created new enumeration MyFakeEnum

    this would be the basis of every checkin comment and then the developer could add to it with specifics or just modify the text to be more explicit or supply reasoning or whatever.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Change changeset being compared.

    XCode has a nice feature during comparing files.

    It lets you change the one on the right side (so the one from version control with a slider),

    The effect is that you can easily find the spot in time where something has changed. Such feature would need the positions in both files to remain stable (so not jump to the top).

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close