• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 5.0
    • None
    • Plan Branches
    • None

      The atlassian connector plugin for IntelliJ idea is a phenomenal way to keep up with the tests being run in your code as you develop. I use it all the time.

      We have just moved to an automatically detected plan branches configuration on bamboo, which enables even more automated testing, but now the plugin doesn't show me the branches that are being tested.

      Could there be support for plan branches in the IntelliJ plugin? Better yet, could it be branch based, instead of plan based? (meaning, I would like to click on a branch and see all the test plans being run on it). This is the frequent use-case.

        1. list.png
          list.png
          67 kB
        2. settings.png
          settings.png
          157 kB

            [BAM-12850] IntelliJ plugin does not support plan branches

            Thanks

            James Dumay added a comment - Thanks

            Janusz is off to the end of the week. We will let you know if it works fine next week.

            Thanks,
            Jacek

            Jacek Jaroczynski (Inactive) added a comment - Janusz is off to the end of the week. We will let you know if it works fine next week. Thanks, Jacek

            Not yet. We have a hot conversation how it should be implemented. It appeared that finding first commit in the branch is extremely hard for Git.

            Jacek Jaroczynski (Inactive) added a comment - Not yet. We have a hot conversation how it should be implemented. It appeared that finding first commit in the branch is extremely hard for Git.

            Phenomenal, looking forward to see it.

            Mauricio Carneiro added a comment - Phenomenal, looking forward to see it.

            I'm glad you like it.

            I'm not sure how you're going to decide which branches belong to you (commit authorship?)

            I think that author of the first commit is the best candidate for branch "owner".

            meaning I could see all tests being run for a given branch by expanding it in the interface

            Definitely. Every plan branch would work in the same as a standard plan so you would be able to see details and tests results.

            Jacek Jaroczynski (Inactive) added a comment - - edited I'm glad you like it. I'm not sure how you're going to decide which branches belong to you (commit authorship?) I think that author of the first commit is the best candidate for branch "owner". meaning I could see all tests being run for a given branch by expanding it in the interface Definitely. Every plan branch would work in the same as a standard plan so you would be able to see details and tests results.

            Hi Jacek, thanks for looking into this.

            I really like your suggestions, especially the group by branches option and the 'show only my branches' option, although, I'm not sure how you're going to decide which branches belong to you (commit authorship?).

            I'd be happy even if we had to see all branches, but ideally, seeing only my branches, and grouping by branch (meaning I could see all tests being run for a given branch by expanding it in the interface) would be perfect.

            I agree that branches come and go quickly, so selecting them manually would be cumbersome. Automatic detection for those who opted-in (choosing show plan branches or show my branches) is the best way to go IMO.

            Mauricio Carneiro added a comment - Hi Jacek, thanks for looking into this. I really like your suggestions, especially the group by branches option and the 'show only my branches' option, although, I'm not sure how you're going to decide which branches belong to you (commit authorship?). I'd be happy even if we had to see all branches, but ideally, seeing only my branches, and grouping by branch (meaning I could see all tests being run for a given branch by expanding it in the interface) would be perfect. I agree that branches come and go quickly, so selecting them manually would be cumbersome. Automatic detection for those who opted-in (choosing show plan branches or show my branches) is the best way to go IMO.

            Hello Mauricio,

            Thank you for the report.

            We have looked into that and here is a nice and quick way we can add support for plan branches:

            1. Add switch to configuration which could enable plan branches and show "all branches" for selected plans or only branches "owned" by the current user (settings.png screenshot).
            2. If enabled then plan branches would be displayed in the plan list view (list.png screenshot). We could also add grouping by branches to make the view "branch based" (IntelliJ IDEA only).

            We think that plan branches can appear and disappear quickly so manually selecting in the Settings page which branch we want to see is not an option. This kind of selection would also introduce some complication to the UI (two levels deep selection list).

            Please let us know your opinion.

            Thanks,
            Jacek

            Jacek Jaroczynski (Inactive) added a comment - - edited Hello Mauricio, Thank you for the report. We have looked into that and here is a nice and quick way we can add support for plan branches: Add switch to configuration which could enable plan branches and show "all branches" for selected plans or only branches "owned" by the current user ( settings.png screenshot). If enabled then plan branches would be displayed in the plan list view ( list.png screenshot). We could also add grouping by branches to make the view "branch based" (IntelliJ IDEA only). We think that plan branches can appear and disappear quickly so manually selecting in the Settings page which branch we want to see is not an option. This kind of selection would also introduce some complication to the UI (two levels deep selection list). Please let us know your opinion. Thanks, Jacek

              Unassigned Unassigned
              10b429b7ca91 Mauricio Carneiro
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: