531 results found

1. Disable the Client caching of the user/password.

   We will like to see the window login on every launch.

   4 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. Clarify the origin of the error on distributed scenarios

   See my post here about a problem I had:

   http://www.plasticscm.net/index.php?/topic/1072-disk-full-error-when-trying-to-sync/page__fromsearch__1

   1 vote

   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  ·  Edit…  ·  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. Autodetect xlinks when creating sync view

   To avoid mistakenly adding multiple xlink targets to the same source when creating sync views and to make sync view creation to repos with xlinks easier I suggest that the sync view editor should be "target" centric, not "source" centric:

   I click add new sync view.
   Instead of clicking add new source as I am supposed to now, I click "add new target".
   I choose the target on a target server.
   Plastic detects that I already have a repo with the same name on my source server (or use some other similarity measure as I have suggested above) and ask if I want to use that source repo, another source repo or create a new.
   Plastic detects that the target repo has xlinks. For each xlink Plastic repeats the above check for a source repo and offers to use that, another or a create a new.

   By using a target first approach, this would eliminate the risk of the above error and be very convenient.
   Combine that with a button for syncing all targets and you have a near perfect sync view system.

   To avoid mistakenly adding multiple xlink targets to the same source when creating sync views and to make sync view creation to repos with xlinks easier I suggest that the sync view editor should be "target" centric, not "source" centric:

   I click add new sync view.
   Instead of clicking add new source as I am supposed to now, I click "add new target".
   I choose the target on a target server.
   Plastic detects that I already have a repo with the same name on my source server (or use some other similarity measure as I have suggested above) and ask… 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

4. diff and merge configuration panel help allows selection out of variables

   Right now the preferences for diff and merge for external tools has a help modal dialog that is difficult to work with. Building the command line is repetition of modify and click on the help to make sure things are being typed correctly.

   Suggest that instead it's a drop down dialog that populates the variable into the edit box as selected.

   1 vote

   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  ·  Edit…  ·  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. Shell extension - mark parent dir modified. (a la tortoise git\svn)

   When modify one item, mark parent directory modified.

   11 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

6. Better issue tracker API

   Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.

   Create branch from ticket
   I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made even better if the API could make the extension provide a list of filters to choose from.

   It is not that it is a big issue to use the branch naming convension, but it would allow a more smooth workflow if the list of tickets was integrated with branch creation.

   Two way state synchronization
   I was also surprised that the extension seems to be a one way system with no support for adding states or comments to the ticketing system.
   I had expected to find a "hook" to branch switching or creation. That way it would have been possible to change ticket state from say "new" to "open".
   If the ticket properties, especially state, were synchronized with Plastic attributes, it would provide a very convenient way of filtering branches when integrating completed tasks for a build.
   If there was a "hook" for changeset comments, changeset comments could also be added to the ticket comments. This would provide possibilities for a detailed change log.
   Two way states and events on commits, branch switches, etc. is what I miss the most.

   Caching
   I would benefit performance if every branch explorer refresh didn't caused a complete loading of all issue tracker tasks in view. You might expect the branch explorer to attempt a refresh if you hit the refresh button, but it the refresh fails, for example if you are offline or the ticket server for some reason is not available, then all your ticket titles disappear. This is a problem if you have adopted a ticket id branch naming scheme. It would be better, if Plastic cached tickets and only replaced titles if a new was actually loaded. Also, why is the extension asked to load a ticket both by the branch explorer and when clicking on a branch?
   I do however realize that the extension could do such caching by itself, but it would be easier to develop extensions if such behavior was implemented in the calling system.

   Repository mapping
   I found the repository to ticket system project mapping a little clumpsy in the API. E.g. when refreshing the branch explorer, the extension is asked to load tickets for all visible branches, but with the empty string as repository name. Only when clicking on a branch, the repository name is provided. There is probably an explanation, but it made it hard to map repositories with projects in the ticketing system. This is a problem for ticketing systems like YouTrack, where the project name (in short form) is part of the ticket ID and IDs within projects are sequential (i.e. non-unique globally).

   Auto comments
   In Plastic preferences you can setup auto-comments. You can choose between user name and date. This is almost entirely useless since that information is already baked easily available.
   When using build servers like TeamCity, you get some nice links to your ticketing system if you refer to ticket id's in the comments. A typical workflow is making a solving a bunch of tickets and then integrating the branches in a build branch that the build server will use to generate a new build. In the process of integrating branches, it would be helpful if the comments automatically the ticket ids, since this would make a full circle between the VCS, Build server and ticketing system. Manully entering these comments is tidious and error prone, since it is often only a matter of repeating branch names and ticket titles.
   It would be nice if the "custom" auto-comment formatter was extended more tags. Most obvious are branch name, ticket title, ticket id, ticket description.

   Here are a few ideas for an improved issue tracker API. These suggestions were first posted in the forum 05 December 2011.

   Create branch from ticket
   I was surprised that I could not create a branch from a list of tickets. Instead I have to use a branch name convension to link my branch to a ticket. It should be trivial to extend the extension API with a "load tickets" method and present the list of tickets when creating a branch. How to select the tickets to be shown could be a matter of extension configuration. This could be made… more

   13 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. add a cherry pick without link option / or allow delete of cherry pick links

   It happens from time to time that you think you are working on some branch when actually you are on another.

   What I usually do in such a scenario is:
   1. check in on wrong branch.
   2. switch to correct branch.
   3. cherry pick from wrong to correct branch.
   4. copy the merged file(s)
   5. delete new change set created on correct branch created by cherrypick.
   6. copy the files back to the workspace (or just paste from clipboard if it was a single file).
   7. check in the changes (now properly set in the correct branch).
   8. delete the unwanted changeset that was created on the wrong branch.

   If I could do the chery pick without leaving a link or if I could delete the link after performing the cherry-pick I could then just delete the miss-placed changeset and that's it.
   Currently this is not possible because the existence of this link prevents me from deleting the changeset that was miss-placed in the wrong branch.

   It happens from time to time that you think you are working on some branch when actually you are on another.

   What I usually do in such a scenario is:
   1. check in on wrong branch.
   2. switch to correct branch.
   3. cherry pick from wrong to correct branch.
   4. copy the merged file(s)
   5. delete new change set created on correct branch created by cherrypick.
   6. copy the files back to the workspace (or just paste from clipboard if it was a single file).
   7. check in the changes (now properly set in the correct branch).
   8. delete the… more

   2 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

8. add replication source

   in the branch explorer, have the ability to specify a replication source, instead of having to pull a branch from a source before it showing up in the list.
   This way it would be easy to add all the local developer repos as replication sources to a new team members BrEx in a distributed scenario, without having to pull something from every local developer repo.

   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

9. Merge as an atomic operation

   There might be some use-cases out there for not wanting to do this, When I merge one branch into another branch, if I make a change in between finishing the merging and checking in my changes, that change becomes very difficult to trace as to when it happened. If that change breaks something it becomes nasty to track it down and then revert it.

   There are probably use-cases where people wouldn't want that behavior but I'd like to be prompted to go to pending changes and check-in my merge once it's finished.

   3 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. Provide a public interface to your bug tracker so customers can see what issues are being worked on, which are backlogged, etc.

    It would be nice to see the status of bugs, features, enhancements, etc. and where they are (backlogged vs implementation, etc) and in which release candidates they are scheduled.

    4 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. provide an increased level of support for the eclipse ide platform.

    Basically the visual studio plugin for PlasticSCM is very powerful, however the majorly popular Eclipse IDE open source platform plugin is very very limited. I'd like to see an increased level of support for this platform as I'm sure many others would as well.

    13 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

12. Fix scroll-bar in source diff window

    need to set mouse capture when scrolling in source diff window. Otherwise if your mouse moves outside the scrollbar (most likely horizontally), it stops scrolling, and you need to go back and click and drag to scroll.

    4 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

13. Group workspaces (and repositories)

    I would like to see a way to group workspaces (and repositories) in order to make the list more readable.

    As i use the model one workspace for a project or component, i got to many for a readable list.

    Tagging them with a keyword and show them as a tree would make it easier to find workspaces.

    27 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

14. Show a list of files on "add tree to sc" action

    Show a list of all files before you add them to the source control. sometimes i need to keep a file back for some reason and add it some time later.
    Also the add tree to sc action is very opaque. it doesn't even create a new changeset!!! i never know which files i realy added.

    1 vote

    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

15. Change the comment seperator

    Hi, please change the comments seperator from "" to something less frequently used. We have A LOT of files with a "" in the file name and refering to them in a comment isn't that easy when "_" is the seperator ;)

    1 vote

    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

16. Add an option to the server to check database consistency

    I would like to see an option that scans the database for corruption or inconsitencies. Now i have to rely on the gui to crash or bahave strange to see that there is something wrong.

    A periodically scheduled job, a short report and a big green light that everything is OK would be good for my trust in the plasticscm.

    0 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

17. In branch explorer, allow a changset to be dragged from one branch to another to merge it whereever you want.

    This would make merges much slicker, by saving all of the RMB clicking.

    23 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. Add Auto Update Check

    Could you add an option to automatically check/alert on updates of PlasticSCM? (and display the version number somewhere).

    To see if there is a new version (and there are often because you guys seem to work hard ;-), I have to examine the properties of one of the exe files and compare it with the version in the on-line changelog.

    65 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
    AdminCodice Software (CEO / Founder, plasticscm) responded

    Plastic SCM 10.0.16.5668
    https://www.plasticscm.com/download/releasenotes/10.0.16.5668

    Windows – Plastic: Auto-update!

    Now you can update Plastic on Windows to the latest version from within the application itself.

    When Plastic detects that a new version is available, the help panel will display a notification telling you which version is available. On the help panel is a link to download the latest version.

19. After a Code Review for a branch, add an icon (e.g. a check, a pending sign, ...) to the branch in Branch Explorer

    After a Code Review for a branch, add an icon (e.g. a check, a pending sign, ...) to the branch in Branch Explorer

    105 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

20. Add ability to select font size in the preference dialog

    Have a global setting of font size (and maybe also typeface) that will be implemented accros all windows

    1 vote

    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  ·  Edit…  ·  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