526 results found

1. Plastic SCM should show the relative git commit hash on the Branch Explorer Options window

   It would be really nice for us who are using the GitSync feature to be able to know in Plastic the Git hash of a changeset. :)

   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

2. Switch/Update should include metadata for cloaked items

   As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.

   If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.

   Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items in the same directory and you want to update just one of them. (If metadata is fetched you can perform a "cm update --cloaked <item>" to update just one item at a time. However, if metadata is not yet available you can only do the update on the parent folder, which would update all the cloaked items at the same time.)

   I suggest always fetching metadata for cloaked items, to improve consistency. For cloaked folders, it would be sufficient to fetch metadata for the folder itself, not for the sub-tree below it (for performance reasons).

   As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.

   If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.

   Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items… more

   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

3. Smarter loading of changesets in "Explore changesets on this branch"

   When selecting "View - Explore changesets on this branch", sometimes the message "This branch has a large number of changesets ... Continue?" pops up AFTER a lengthy calculation and if "Yes" is pressed, the "Branch Changes" window is then displayed instantly! ;)

   Taking a hint from TortoiseSVN, you could load only the latest 100/1000 changesets or so, and then have buttons to "load 100 more" and/or "load all"...

   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

4. Change the wizards and profile creation to allow working mode and credentials to be changed/overridden

   You used to be able to specify the working mode and credentials (username & password) when configuring the client and creating profiles. Now, if the server is set to ADWorkingMode it forces the client to also use ADWorkingMode and forces th userid & password to the local domains credentials. This makes connecting to plastic server from remote locations problematic and rather difficult to achieve. If you could still simply change the client to LDAPWorkingMode and profile username/password it would be much easier to accomplish this.

   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

5. Make Diff listen to file-change-notifications and ask to reload

   The Diff view/window in Plastic does not listen to filesystem notifications about file-changes when diffing a file in a workspace.

   It should discover external changes to the workspace file and ask to reload/recalculate the diff when needed. Other Diff tools I have tried do this...

   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…)
   3 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. Search in Branch Explorer should include Branch Comments

   The filter box in the Branches view gets hits on words in the branch comments, but the Search box in Branch Explorer does not.

   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

7. Improve the conditional format to support to coloring of branches with un-replicated change sets

   I want it to be possible to color branches that have change sets that have not been pushed to some other server via sync replication.

   To be specific and explain the background:
   I use jenkins to do some builds of my project when the main branch has been pushed to a central repository.
   it has happened to me several times that I checked in code (locally) and executed the jenkins project just to discover that it ran old code because my main was not replicated to the main server.

   I would be happy if my main branch would show with some color if it has change sets that have not been replicated to a specific replication server.
   (coloring all the other branches that have not been pushed is also o.k.)

   I want it to be possible to color branches that have change sets that have not been pushed to some other server via sync replication.

   To be specific and explain the background:
   I use jenkins to do some builds of my project when the main branch has been pushed to a central repository.
   it has happened to me several times that I checked in code (locally) and executed the jenkins project just to discover that it ran old code because my main was not replicated to the main server.

   I would be happy if my main branch would show with… more

   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

8. Add home button to 'Branches' tab

   Add the home button like the one in the Branch Explorer to the Branches tab. This makes it much easier to jump to the current branch especially when being on a higher level branch.

   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

9. Add support for branch depth in find branch command

   I propose adding a "depth" or "level" filter-option for the branch find-object, to filter on branch namespace-depth (just like "Display branch levels" in Branch Explorer Display Options).

   Example:

   find branch where level < 3

   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

10. Indicate whether or not a changeset / branch has been synced from the Branch Explorer

    Do something (change color, icon, etc) to show that changesets/branches have not been synced.

    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

11. layout branches in branch explorer by attribute

    I use the manual relayout mode to layout my branches in a way, that release branches are on top, the trunk is in the middle and all issue branches are below.
    This way I have a fast overview of the changes that are released.
    [They also have different colors ;)]

    All these branches have an attribute called "role" with different values:
    "Release" for releases
    "Trunk" for the trunk
    "Patch" for issues

    Now, it would be VERY nice if I could teach the branch explorer, that branches should be layed out in an order (top to bottom) based on the attribute "role".

    I use the manual relayout mode to layout my branches in a way, that release branches are on top, the trunk is in the middle and all issue branches are below.
    This way I have a fast overview of the changes that are released.
    [They also have different colors ;)]

    All these branches have an attribute called "role" with different values:
    "Release" for releases
    "Trunk" for the trunk
    "Patch" for issues

    Now, it would be VERY nice if I could teach the branch explorer, that branches should be layed out in an order (top to bottom) based on the attribute… more

    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

12. Track the evolution of a section of code back through revisions

    This overlaps with the existing version tree functionality in Plastic, and with the existing annotations functionality - and is probably related to method history too.

    My use cases are:-

    1. I see a piece of code that is broken, but don't know anything about what that code did in the first place, when it was introduced or who did it, and what were the checkin comments.

    2. Again, I see a piece of code that is broken, and I want to jump straight to the diff for that piece of code in whatever revision introduced the breakage. If that revision turns out not to be the one that broke that code, I want to jump back further without seeing other revisions that had nothing to do with that section of code.

    What I'm looking for is some way of focussing on a specific section of code and going back over revisions to see how that section of code changed, and ultimately how it got in the first place.

    For added value, I'd like to track that section of code as it moves around a file or across files.

    I've see annotation GUIs in other VCS offerings that allow a progressive jump back by line - this addresses my use cases for 80% of the time.

    Occasionally I'd like to track code motion too - so maybe some method history using the Semantic Outline mechanism would be good?

    Alternatively, could there be an option in the file 2-d history view to lock on to a line in the preview pane - that would be awesome, and I think that if Semantic Outline is enabled with analyse refactors, it would cope with code motion too.

    This overlaps with the existing version tree functionality in Plastic, and with the existing annotations functionality - and is probably related to method history too.

    My use cases are:-

    1. I see a piece of code that is broken, but don't know anything about what that code did in the first place, when it was introduced or who did it, and what were the checkin comments.

    2. Again, I see a piece of code that is broken, and I want to jump straight to the diff for that piece of code in whatever revision introduced the breakage. If that revision turns out… more

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

13. Add support for wildcards for repository names in lock.conf

    Currently, it is not possible to apply the same set of rules to multiple repositories, or indeed all repositories. My request is to add support for wildcards in repository names, so a set of rules can be made to affect multiple, or all repositories on the server.

    Eg.
    rep:* lockserver:my.lock.server:8087
    *.fbx

    Should make locking required on all fbx files on all repositories.

    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

14. interactive annotate view

    Interactive annotate view which allows to user to select two revisions to annotate between. This is similar to perforce timelapse view. A similar request is marked as completed although the implemented functionality is quite different and does not allow the user to easily annotate between two revisions.

    https://www.perforce.com/support/tutorial-video-library/video/using-time-lapse-view

    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

15. split diff view among 2 or 3 monitors

    It's very tough to examine diffs on a single monitor. You have 3 panes, Semantic View on the left, source in middle, and changed on the right. You wind up having to scroll all over the place. Most developers have two monitors, and many like me have three. What if you could hit an "Expand" button and one monitor would display source view full screen, and the other monitor was destination view? Optionally, the third monitor would show Semantic View and the top pane of changed files would be on all of the views. Considering the fact that Plastic is used 50% of the time for viewing diffs, I think this would be an enormously exciting new feature and product differentiator.

    It's very tough to examine diffs on a single monitor. You have 3 panes, Semantic View on the left, source in middle, and changed on the right. You wind up having to scroll all over the place. Most developers have two monitors, and many like me have three. What if you could hit an "Expand" button and one monitor would display source view full screen, and the other monitor was destination view? Optionally, the third monitor would show Semantic View and the top pane of changed files would be on all of the views. Considering the fact that Plastic is… more

    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. Show Deleted files in Items option

    An option to show deleted files in the Items list/treeview

    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

17. Keyboard shortcuts in the diff viewer don't always work

    The issue refers to the diff viewer window. The CTRL + + and CTRL + - keyboard shortcuts are handled globally within the window, no matter where keyboard focus is. On the other hand, the CTRL + M and CTRL + N (and their counterparts with Shift pressed) work only when keyboard focus is in the diff pane on the bottom.

    The problem is that when you want to go through a code review, you have to click the diff pane whenever you switch to another file. Please check it by yourself: open the diff viewer, press CTRL + + and then try to use any of the other shourtcuts to move through the changes. They won't work. It makes code reviews painful.

    I will be grateful if you fix it. Thank you!

    ---

    There actually was an existing topic for the issue, but it was declined because of a misunderstanding, I guess (https://plasticscm.uservoice.com/forums/15467-general/suggestions/10643718-forward-prev-next-diff-keys-to-inline-diff-from-pa). The topic was wrongly considered to be a duplicate, but the thing is, the issue in question was related to something else.

    The issue refers to the diff viewer window. The CTRL + + and CTRL + - keyboard shortcuts are handled globally within the window, no matter where keyboard focus is. On the other hand, the CTRL + M and CTRL + N (and their counterparts with Shift pressed) work only when keyboard focus is in the diff pane on the bottom.

    The problem is that when you want to go through a code review, you have to click the diff pane whenever you switch to another file. Please check it by yourself: open the diff viewer, press CTRL + +… more

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

18. Integrate Plastic Cloud with third party services (such as Unity Cloud Build)

    Plastic Cloud is nice but it is today a cloud-hosted service that does not communicate with any other cloud-hosted services. I would like to see that it is possible to hook other services up directly to Plastic Cloud repos.

    The most straight-forward way to do this would probably be to provide a GitSync solution -- it would immediately allow Unity Cloud Build, Slack and many other integrations to work without additional work on your part. If there are difficulties when creating a two-way GitSync solution for Plastic Cloud then a read-only Git API would enable most integrations to function.

    In the interim, I will set up a Plastic server on a machine in AWS/Google Cloud. This server will be a replication slave. I will integrate any cloud services against GitSync on this server. Hope to be able to eliminate the extra Plastic server in the future.

    Plastic Cloud is nice but it is today a cloud-hosted service that does not communicate with any other cloud-hosted services. I would like to see that it is possible to hook other services up directly to Plastic Cloud repos.

    The most straight-forward way to do this would probably be to provide a GitSync solution -- it would immediately allow Unity Cloud Build, Slack and many other integrations to work without additional work on your part. If there are difficulties when creating a two-way GitSync solution for Plastic Cloud then a read-only Git API would enable most integrations to function.

    In… more

    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…)
    3 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. Expose plastic triggers as web hooks (via the WebAPI)

    This would enable all the popular interoperability that other development operation tooling makes available... also opens up the possibility for the community to contribute Zapier Zaps and IFTTT recipes.

    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

20. Allow to undo the current selection in Gluon (just like Plastic GUI)

    In Plastic GUI you can either undo the current selection with a right click, or undo all the checked items with the undo changes button.

    Allowing the same behaviour in Gluon would be really appreciated.

    Thank you,

    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