General

General

Categories

JUMP TO ANOTHER FORUM

  1. Is one of the most used IDE of the JAVA development and is the one i use more because of his GUI designer, feature that eclipse doesn't have for free or erent enought good

    60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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. I wanted to be able to quickly see (within the branch explorer) branches that have changesets after the last merge in the branch.
    An enhancement could be to do this only for child branches of a specific branch.

    As I described here:
    http://www.plasticscm.net/index.php?/topic/876-highlighting-un-merged-branches/page__fromsearch__1

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. I would like to see Plastic SCM have support for TestTrack Pro issue management system. See the following link to add support using TestTrack's SDK for C#: http://labs.seapine.com/wiki/index.php/TestTrack_SOAP_SDK_Tutorial_-_C_Sharp

    For more information on TestTrack, go here: http://www.seapine.com/ttpro.html

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. As far as I can see, the GUI is missing the useful --ignore options from the command line.

    22 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  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. For the PSCM GUI, check-in's seem to take a long time meanwhile locking the main ui thread. Executing the check-in command in a seperate thread would be really nice and a progress bar to show at the status bar would be even better.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  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. When selecting a changeset, I'd like to have a preview area where the changeset's details are shown (at least which files have been changed). Currently, I have to double click a specific changeset in order to see the details.
    Think of an email client like Outlook, where you can read the mail by selecting it in your list of mails without opening the mail in an extra window.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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. During a lengthy operation (Update/Switch), I would like to be able to continue working on another of my workspace tabs. As it is, the Update/Switch dialog is modal and I have to wait for the operation to finish before I can switch tabs.

    13 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  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. When creating a code review with files that have been merged into the branch it (sometimes) properly categorizes them as CC "Changed in merge source and destination). However, the diff does not show which lines came from the source and which were change in the destination. It would be great to have those separated out for easier code review.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Ability to apply color to branches (simple but usefull tool). All of us works on separate branches and we have as well our "under dev" or task specific branches. We merge from and to only using our main branches. Colorcoding is very intuitive way to differentiate "development/beta" branches from final branches

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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. The conditional format and changeset colours are currently per workspace. It would be nice if all my workspaces were consistent and I didn't need to configure them all manually.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  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. Sometimes you may start working on the main branch unaware without creating a child branch first. You get in trouble if your dirty changesets are used by others.

    A good solution to protect the main branch from accidental check-ins is to deny users the check-in right on main branches. To perform a check in from their child branches they will have to log in as a different user (as an 'integrator').

    The problem is that it is cumbersome. You have to run the Plastic SCM client configuration wizard to log in as an 'integrator' and then remember to switch back…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Repo / workspace names will not fit in the workspace tabs if using long descriptive names.

    This becomes worse when using the feature of "sub-repositories". When having several subrepo workspaces we could end up with only the parent repo name visible in the workspace tab.

    I'm aware that I can rename workspaces, but it would be better if the tab widths were not so restrictive.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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 I get told I can't delete a branch "because it has revisions". I appreciate the warning, but it should allow me to say "ok, delete the revisions too" rather than cancelling the delete. Deleting each changeset manually to allow the branch to be deleted is a pain.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. A number of forum and uservoice conversations show that XLinks in their present implementation are not sufficient for common scenarios of component-based or modularized development. While XLinks may be an elegant and powerful idea, they are not a replacement functionality of working with subtrees provided by virtually every other system, from SVN to Git and including Plastic SCM 3. Further, a basic solution can be implemented in Plastic 4 with shell scripts and cloacked.conf. Some native means of working with components in subtrees of a repository would be very useful.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We consider Xlinks a powerful enough solution for component oriented development in its current form, and most of the customers agree.

    Git support is no better at all (it is quite weak compared) to Xlinks (you’ve to handle the dependencies manually with Git).

  17. Please port the v3 vss import wizard to v4.

    The route by vss2git failed big time probably on a binary in vss. The route by svn is also far from flawless (I could not even exportmy error free vss to svn).

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. It would be nice to be able to define visibility rules per workspace and not per repository.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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. Seems many people save xml files as 1 huge long string. This makes line by line comparison rather worthless. If SemanticMerge could parse xml this would make comparison and merge of xml files so much better.

    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  ·  Flag idea as inappropriate…  ·  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. This is a follow-up to the following uservoice:
    http://plasticscm.uservoice.com/forums/15467-general/suggestions/7422880-facilitate-creating-a-new-workspace

    Now that there is a setting DefaultWorkspaceRoot in guiclient.conf, please update that with the latest one entered in the New Workspace dialog. That way a user will not have to manually edit this setting.

    (BTW, when I told one of my coworker that there is a setting for this in the conf file, the reaction was: "I know, but this is ridiculous. The program should update that setting automatically!")

    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  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for the suggestion, but I don’t think the behavior you propose is the right one.

    By default Plastic already proposes a place to store workspaces. Chances are 99% of people will simply keep their workspaces there, since it is just a place inside the home directory.

    Maybe some teams need another place for this, then it is probably fine for them to edit the default.

    I understand it would be fine to simply use the last path users entered, but then why should we have a configurable “root”? We did this because many teams want this to give a default setting to their users, specially on huge teams.

    Then, you can probably skip and create a workspace on a different location but: should it really be the new default? Maybe you just occasionally skipped the default place but you want to keep it for the rest of your workspaces……

← Previous 1 3 4 5 6 7 8
  • Don't see your idea?