Skip to content

General

General

Categories

535 results found

  1. Sometimes when looking at a code review making comments against individual lines is not appropriate. The implementer might have got the design/architecture or pattern wrong. It would help to be able to record a comment at a top level against the review to allow an audit trail without having to go through all the line by line comments. For example. Design and implementation ok, no security has been considered and there are weaknesses so needs rework. Minor code comments as recorded, but review abandoned due to high level issues.

    30 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)
  2. When right-clicking a Private Ignored item, the "Add to source control" action is shown but disabled (grayed out). That's frustrating as there is no real reason to disallow this!

    Scenario: You have ignored all *.dll files, since you build them. However, there is a specific 3rdparty DLL that you would like to make Controlled (put under source control). To do this, you would now have to edit ignored.conf, "Add the file to source control", then undo your changes in ignored.conf. If the above command was not disabled for ignored items it would have been one click in the context menu,…

    5 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. In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This option should be available in the Windows shell extension as well.

    The following related uservoice should apply here too:
    http://plasticscm.uservoice.com/forums/15467-general/suggestions/10027482-items-view-allow-diff-of-private-files-as-well

    3 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  ·  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. In 5.4.16.694 a new option was added to diff two selected items in the 'Items 'view. This currently only works for two Controlled files or two Controlled folders.

    It would be great to have this work for two Private files (or one Controlled and one Private file) as well. You would have to do some detection of txt/bin filetype on the Private files.

    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)
  5. In the Repositories view, very little information is displayed about the repositories listed: Name, namespace/hierarchy, server. That's all.

    When I list my repositories I want to see something similar to the Branches view: Owner, Creation date, Comment

    (The Comment field was requested in another uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/8063376-repository-description)

    But most importantly, I'd like to see number of branches, number of labels, number of changesets! This info could be displayed in an "extended information" sidebar, also just like in the Branches view.

    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)
  6. Let the user undo a checkout without loosing the modifications themselves. The result would be a file with status "Changed".
    Neither the content nor the file's timestamp should change by this operation.
    Currently, undoing a checkout always results in downloading the versioned content.

    13 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 looks that currently MergeTo operation is ignoring --mergetype parameter. If only automatic merge of changes from both source and destination is possible Plastic is doing it.

    It would be good to have a chance to explicitly show that changes only on one side are allowed and exit with failure if there are some also at the other.

    Additionaly for now it is not possible to give comment which will be used for check-in operation after successful mergeTo.

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

    On the release 7.0.16.2077, we added the new server-side merge that extends the existing merge-to functionality.

    Using the server-side merge, the file conflicts can be resolved and the merge resolution options (—mergetype, —keepsource & —keepdestination) are supported.

    The server-side merge is still on preview so you need to enable it adding the following setting on the client.conf. Check how to do it on the release notes: https://www.plasticscm.com/download/releasenotes/7.0.16.2077

    Remarks, the server and client version must be equal or newer than 7.0.16.2077 to use the server-side merge.

    We comment option will be documented soon, we already plan a task to do it in the next few weeks. Sorry for the delay.

    Best regards

    Borja

  8. 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

    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. User A changes revision type of an item from binary to text. User B runs update and refresh of items list, but item remains binary. Pressing CTRL+D shows a dialog that quotes "Error: Differences between items of diffente types cannot be calculated". That implies that the change of User A was sent to the server and applied to the item, but the information is not propagated to the other users.

    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)
  10. Definition: when I refer to a repo "hiearchy", I mean some repo ("the top" level repo) and all of the repos xlinked below it (those repos may contain xlinks to repo, thus the "hierarchy").

    Today, if you have a large and complex repo hierarchy, it make it very difficult to work distributed.

    Use case: A "top" level repo than contains in it's referenced "repo hierarchy" 200-300 other repos via xlink. These other repos may be several levels of xlink deep. The purpose of all of the xlinks is component/reuse structure of coding.

    While creating such a repo on a central…

    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)
  11. This would be very useful for learning and experimenting with the query syntax, and for quickly adding/adjusting a query without having to remember syntax.

    It should be possible to build the query by selecting the different targets etc and adding/removing/editing filter specifications. The resulting query text should be displayed.

    5 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)
  12. The "Explain Merge" functionality is currently only available while performing a merge, and not in retrospect when looking at an existing changeset containing one or more merges.

    I suggest adding this functionality to the "Diff changeset" view as well. it could be activated by context menu on a "Merged from ..." changelist header.

    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)
  13. Display a "+" or similar at left/right end of branch in Branch Explorer, when it has been truncated by the date-filter.

    5 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)
  14. The default ordering of branches in Branch Explorer could be improved. It should respect and make use of the branch hierarchy, so as not to cross lines unnecessarily.

    When I have several top-level branches with some child branches each, they are not grouped together vertically in a hierarchically logical order. Instead they seem to be randomly placed (?) leading to a lot of lines crossing each other. (I always enable "Display cross-branch changeset links" which makes this more obvious.)

    I think child branches should always be displayed below their immediate parent (or sibling if multiple children overlap in time).

    14 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)
  15. In Branch Explorer / 2D Version Tree, replace the "Options" toggle button with the same "Show extended information" icon button as in other views.

    Also, make the "Show extended information" icon button a "toggle button" in all views.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  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. When creating a branch from an issue tracker task/ticket, the ticket title description is added as the branch comment.

    When merging back from such a branch it would be very useful if the branch comment was displayed in Pending Changes (along with the branch name on the Merge Link and on the title of the Merge Changelist). Otherwise you only see the ticket number from the branch name (/main/trac5877 or similar).

    The same goes for the Diff Changeset view, and possibly some other views as well. Display the branch comment along with each merge changelist header.

    3 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  ·  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 are a couple of things I'd like to see added in the "Branch history" table inside the Branch Properties view:

    • The "Source changeset" cell for the "Creation point" row should include the source branch, just as for the "Rebase from" rows. This would make it easier to see where a top-level branch was forked from, and even for child branches it would be more consistent. (Only changesets on the current branch should omit the branch name.)

    • In the context menu for the rows in this table there are "Diff ..." and "Browse ..." commands. I'd like add 2 more…

    3 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  ·  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. 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…

    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)
  19. Have option to have to confirm a check-in operation.

    The use case is that because the refresh pending changes button and the check-in button are so close together, some users accidentally click the Checkin button when they mean to click the refresh.

    Some users would certainly find the extra confirmation annoying, so if implemented, this should definitely be an option controlled via Preferences.

    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)
  20. 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

    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)
  • Don't see your idea?