Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

531 results found

  1. And SSO with Crowd in the webUI.
    Or at least a way to write our own authentication plugins.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  2. When renaming a repository, workspaces created from this repository break. It would be handy if they would automatically retarget to the new name.
    Additionally, renaming a repository will also break with trigger filters, it would also be handy if they would automatically retarget :)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The default keyboard shortcuts are ... interesting at times. Would be great if I could configure them to my liking.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. I know this goes against the branch per task ideology, but sometimes people work on a bunch of stuff in a branch and then merge a larger chunk of work, e.g. a bunch of helper functions etc.

    It would be nice if there was a way in the GUI to automatically gather all checkin comments since last merge / branch creation into the merge comment. I could then edit this comment before merging.

    So for example if I make checkins "fix foo" and "fix bar", my merge comment would be "fix foo\nfix bar".

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. This happens all the time. You do some modifications, hit checkin, get told you need to merge beforehand, you do that and it's all automatic and nice and then you hit checkin again and notice the comments are gone.

    The comments are of course in the history, but I have had to edit them exactly 0 times after the merge. Would be a nicer user experience if the comment was kept there by default (or at least have an option for doing so).

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  6. Similar to "make active workspace" in workspaces, there should be a keyboard shortcut for switching branches.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. It will be useful to have possibility to shelve changes made in "main" repository even if some of files which are changed are located in repository connected by read only xlink. Now shelve is treated in the same way as checkin and it is not allowed to do such operation

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  8. The internal source code viewer is used for displaying diffs only. Add an option to always use it instead of the "Open" / "Open with" to open a single file.

    Why:
    — when browsing a changeset, displaying files that only exist in the source xor destination gives the user a totally different UX than the when a diff is displayed
    — when double-clicking on a file in the "browse repository" view, a heavy-weight application such as Visual Studio is launched, instead of a quick and easy text file viewer.

    In both cases it is slow and impractical.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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).…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. In a distributed development environment (a central server with the 'good' set of source), when you use Replication to Pull a branch you can identify the source repository in the before-replicationwrite trigger from the PLASTICREPLICATIONSOURCE environment variable and the target repository from the PLASTICBRANCH environment variable. In this way you can check that the repositories match and you aren't corrupting your local repository with branches from another repository.
    However, when you Push a branch, there is no way for the before -replicationread trigger to check you aren't corrupting the central repository by matching you local repository name

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  11. Extend the Toggle, Goto Next/Prev and Clear Bookmarks functionality from the Branch Explorer to the Changesets view (and possibly the Branches view) as well. The set of bookmarks should be shared between all the views and filtered accordingly...

    For this to be really useful we first need to get this other uservoice fixed:

    https://plasticscm.uservoice.com/forums/15467-general/suggestions/13217832-persist-branch-explorer-bookmarks-between-sessions

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. When using the repository browser on specific changeset/branch, give ability to download a single folder from that view.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  13. http://<server>:7178/webui/repos

    The list of repositories is shown in creation order (or perhaps by repository ID)
    If you have more than a handful of or repositories, this is a pain, especially since the most used ones are likely to be the more recently created ones, and thus at the bottom of the list.

    Note that in Plastic GUI the Repositories view, Select workspace dropdown & dialog; and for that matter "Open workspace" dialog lists in alphabetical order. as they should. The web should be the same.

    This should be a near-trivial change with immediate benefit. Even better

    • Changeable order (by clicking…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. First: I'm no expert on this, but this is how I understand it.

    Debuggers (WinDbg and VS) on Windows use Symbol Servers for getting the correct .pdb file and Source Servers to get the correct source code while debugging a minidump. This enables debugging of code that you currently don't have in your workspace.

    While Plastic SCM has no contact with Symbol Servers, it should have with Source Servers.
    You may read about it here: https://docs.microsoft.com/en-us/windows/desktop/debug/source-server-and-source-indexing

    In short:
    Debuggers will ask the Symbol Server for the debugging symbols and then the Source Server for the source files.
    To make this…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  15. Currently the "virtual changeset", marked by a dashed circle around your home, will only appear if you have checked out items. However, if you use the "no-checkout"-workflow, you can have changed items that are not checked out, which are pending changes that prevent you from switching branches and so on.
    But the Branch Explorer currently does not show this to you, suggesting that everything is "clean", i.e. you do not have any Pending Changes.

    IMHO, there is no reason to distinguish between "checked out" and "changed" items here, the Branch Explorer should show the dashed marker if you have either.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Integration with Youtrack ???... and I simply hate to sing in and sign out all the time .

    I hate that

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  17. There was already a suggestion of this kind:
    https://plasticscm.uservoice.com/forums/15467-general/suggestions/5657638-add-option-in-pending-changes-to-tell-plasic-that

    But the solution is not very convenient. If we do a refactor there may be a lot of added/deleted items. I simply want to select a pair of added/deleted items then open context menu and select "repair move" or anything equivalent. I already know what has been moved and want to mark this explicitly. Tweaking the similarity so Plastic will find the added file is too complicated.

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. I'm sure it might be possible if there's a way to signal a unity3d editor script to automatically build when a commit is made to a repo/branch. So imagine me taking a secondary computer and just dedicating it to holding my repository/doing unity builds. I've heard of people doing stuff like this with jenkins, but there's probably a practical reason why unity cloud build is so popular.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  19. Really love the progress bar when you switch changesets want to see it in more places, especially the merge from changeset screen, hard to know when my 10GB of assets that I'm merging from are finished downloading until the merge window's start popping up.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  20. When the setup is finished, the client is always started.
    It's a little annoying on servers, where the client isn't setup.
    So please add an option to the last page of the setup 'launch client', just like the 'launch server' that already exists.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
1 2 9 11 13 26 27
  • Don't see your idea?