I suggest you ...

Add a branch weight for layouting in branch explorer

I like to have my branches ordered bottom-up as they are closest to release. So my issue branches are below the trunk which is below release candidates and hotfix branches.

I do this manually right now. So I have two lines für release/hotfix branches then the trunk and then everything else.
This is fine as long as there are only 2 branches in the upper two lines. But sometimes there are more (especially when 'older' branches are updated with new data. Then they overlap.

My suggestion:
Add a weight property to branches (maybe via conditional rules) and order the branches by their weight in the branch explorer. Heavy branches go down and light branches stay up. This would allow me to use the auto-layout and enjoy the right ordering.

9 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SWSBB shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Göran Wallgren commented  ·   ·  Flag as inappropriate

        This is slightly related to this other uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/9655032-improve-vertical-ordering-in-branch-explorer-make

        I find the default visual layout to be rather random. Being able to use a branch-weight attribute for auto-layout would definitely help in improving this.

        (However, as requested in the above uservoice, I would also want the option to order branches vertically by namespace/parentage.)

      • SWSBB commented  ·   ·  Flag as inappropriate

        I would prever if all branches had a default weight (maybe with the value of '10' (with some space up and down), maybe even configurable in the settings)

        Yes! Weight should definitely a private thing.

        Naming conventions don't work for us.

        I love the conditional format rules within platic scm!
        They should work here, too. You could even do the 'naming convention' thing with them ;)

      • AdminCodice Software (Admin, plasticscm) commented  ·   ·  Flag as inappropriate

        Interesting!

        Would you prefer to have weight (then you have to assign it to each branch, which is a little bit painful) or would you prefer to have some sort of naming convention for this??

        And, you want this weight to be private to you, right?

      Feedback and Knowledge Base