Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    BAM-26128Display Plan Name and Branch Name in Bamboo Labels View from <bamboo-url>/bamboo/browse/label/<label>
  2. Suggestion
    BAM-26108Enable Logging of Login/Logout Events in Bamboo
  3. Suggestion
    BAM-26100Ability to dinamicaly update and customize labels from Plans
  4. Suggestion
    BAM-26089Support for Certificate Chains in gRPC Node Communication
  5. Suggestion
    BAM-26084Bamboo ability to execute a single build on multiple Remote Agents.
  6. Suggestion
    BAM-26095Ability to Replace Auto-Generated gRPC Server Certificates with Static, Customer-Defined Certificates
  7. Suggestion
    BAM-26007Integrate GitHub with Bamboo without using PAT tokens
  8. Suggestion
    BAM-3253Ability to modify Bamboo mail subject line
  9. Suggestion
    BAM-13064Allow Gatekeeper to rebase instead of merging
  10. Suggestion
    BAM-20578Support Bamboo in a clustered database environment
  11. Suggestion
    BAM-13409Enable or disable a deployment project and environment
  12. Suggestion
    BAM-20915GitHub repository type doesn't work with anything other than username/password
  13. Suggestion
    BAM-22235Bulk disable Deployment triggers
  14. Suggestion
    BAM-8029STDOUT and STDERR buffering is very annoying
  15. Suggestion
    BAM-782Ability to view the junit test logs
  16. Suggestion
    BAM-3195Hierarchical Project and plan structure in Bamboo
  17. Suggestion
    BAM-3188Clone Project
  18. Suggestion
    BAM-21302Display system-error/system-out elements when viewing a JUnit test case
  19. Suggestion
    BAM-21055Option to set a trigger IP address globally and for all repository types
  20. Suggestion
    BAM-20991Make Quick filters URL shareable
  21. Suggestion
    BAM-20903Improve the variables documentation regarding encryption.
  22. Suggestion
    BAM-20723Switch to daily log rotation instead of file size based rotation
  23. Suggestion
    BAM-20601Possibility to filter and/or sort deployment projects overview
  24. Suggestion
    BAM-20395Add personal filter to deployment projects in the same way as in build plans
  25. Suggestion
    BAM-20358Ability to run a deployment manually without triggering cascaded ones
  26. Suggestion
    BAM-20273Add ability to extend Bamboo Specs across multiple repositories.
  27. Suggestion
    BAM-20098(REST) As an admin, I would like to provide plan name and description on clone endpoint
  28. Suggestion
    BAM-19658Notification for Job Started Event
  29. Suggestion
    BAM-19647Linked Repository Default Permissions
  30. Suggestion
    BAM-15810Bamboo doesn't detect CMake
  31. Suggestion
    BAM-14825Bamboo should not store Stash SSH port in repository definition but rather use the currently configured one
  32. Suggestion
    BAM-14599successful Junit test that have details should be captured in the test summary
  33. Suggestion
    BAM-14533Notification for when build starts
  34. Suggestion
    BAM-14230Stop build without Failing
  35. Suggestion
    BAM-13920Tag when creating a release
  36. Suggestion
    BAM-12165I want to get notification when plan branch is automatically disabled
  37. Suggestion
    BAM-10745"Look in standard test results directory" should say what it considers default as this is not that obvious
  38. Suggestion
    BAM-26034API to manage notifications
  39. Suggestion
    BAM-26137Bamboo shouldn't reach out to repository servers for repository polling triggers if the Plans are in a disabled state or not active state.
  40. Suggestion
    BAM-1223Import Export individual projects / plans
  41. Suggestion
    BAM-2886Environment variables for agents
  42. Suggestion
    BAM-9658Allow administrator to change plan and job keys
  43. Suggestion
    BAM-15411Global expiry configuration for particular deployment projects
  44. Suggestion
    BAM-15415Add "managing agent capability/executable permissions" as a separate permission option
  45. Suggestion
    BAM-15464Provide HTTP(S) authentication method option for Bitbucket Server type repository
  46. Suggestion
    BAM-17403Clean up build working directory similar to the expiry configuration
  47. Suggestion
    BAM-17728Get last timestamp users authenticated in Bamboo and from where
  48. Suggestion
    BAM-17879Bamboo Global Expiry Granular Configuration
  49. Suggestion
    BAM-18336Support NUnit 3.0 format (nunit3)
  50. Suggestion
    BAM-21722Disable or Enable only one type of Specs: Java or YAML
Refresh results
1 2 3 4 5Next >>
1 of 1596
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-26128

Display Plan Name and Branch Name in Bamboo Labels View from <bamboo-url>/bamboo/browse/label/<label>

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Labels
    • None
    • 2
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      In Bamboo, the current labels view only displays the branch name, which can lead to confusion when multiple repositories have identical branch names. Users typically access builds using the URL format: <BAMBOO-URL>/bamboo/browse/label/<LABELS>. This URL shows all builds associated with a particular label, but without the plan name, it's difficult for users to identify which build belongs to which plan.

      • For example, users often have the same branch name across different repositories (e.g., release branches for specific products), and the lack of plan names in the labels view hinders their ability to quickly identify and select the correct build.

      Use Case

      • Users utilize labels to track multiple related builds.
      • Identical branch names across different plans make it difficult to identify the correct build without additional navigation.
      • Including plan names in the labels view will reduce confusion and improve efficiency.

      Suggested Solution

      Enhance the labels view in Bamboo to include both the plan name and branch name. This change will provide clarity and improve the user experience by allowing users to easily discern which plan a branch is associated with, directly from the labels view.

      Benefits

      • Streamlines the process of finding the correct build, especially in environments with numerous plans and branches.
      • Significantly improves the user experience for teams managing multiple repositories with similar branch naming conventions.

        mentioned in

        Page Loading...

              • All
              • Comments
              • Work Log
              • History
              • Activity
              There are no comments yet on this issue.

                Unassigned Unassigned
                bda18cee79a2 Arthur Dantas
                Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Created:
                  06/Jun/2025 9:00 PM
                  Updated:
                  Yesterday 11:23 PM
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian