Open issues

Order by Priority
  1. Suggestion
    BAM-20915GitHub repository type doesn't work with anything other than username/password
  2. Suggestion
    BAM-25731To add SSH keys for Github type repositories and their submodules to use SSH URLS of submodules
  3. Suggestion
    BAM-26134Allow one Bamboo plan to fire build execution of another plan
  4. Suggestion
    BAM-3705Priorities on build plan
  5. Suggestion
    BAM-9658Allow administrator to change plan and job keys
  6. Suggestion
    BAM-15060Create JIRA Issue from failed test is only available to Plan Admins
  7. Suggestion
    BAM-18261 Bamboo should rotate all its log files enabled in a default installation
  8. Suggestion
    BAM-21367Use buildResultKey as the working directory name instead of the buildKey
  9. Suggestion
    BAM-21743Official CIFS/SMB/NFSv4 support in Bamboo
  10. Suggestion
    BAM-25156Allow external AWS SDK dependency for Elastic Agents instance-type updates
  11. Suggestion
    BAM-26135Add Support for Amazon-Linux AMI
  12. Suggestion
    BAM-20219Docker Runner with Windows
  13. Suggestion
    BAM-26089Support for Certificate Chains in gRPC Node Communication
  14. Suggestion
    BAM-26131To send Build status to Bitbucket server on Tags ref key(ref/tags/<tagname>) when build got triggered via Tag Trigger Type
  15. Suggestion
    BAM-26132Add options in Bamboo to allow customizations to the login page
  16. Suggestion
    BAM-16201Audit log doesn't record permission changes
  17. Suggestion
    BAM-22015Show build results in Bitbucket for PR's from forked repo
  18. Suggestion
    BAM-25624As a user I would like to update the build-result.xml path in Bamboo Agent
  19. Suggestion
    BAM-25797Provide option in Bamboo for multiple remote agents to share a common Build working directory
  20. Suggestion
    BAM-26130Queue Multiple Deployments for a Single Environment
  21. Suggestion
    BAM-21066Allow overriding branches for non default repositories in YML specs
  22. Suggestion
    BAM-26128Display Plan Name and Branch Name in Bamboo Labels View from <bamboo-url>/bamboo/browse/label/<label>
  23. Suggestion
    BAM-18453Allow creating / updating linked repositories via REST API
  24. Suggestion
    BAM-19616Ability to transition a plan from Repository Stored Specs (RSS) managed back to a standard plan
  25. Suggestion
    BAM-25811Docker tasks in Ephemeral agents
  26. Suggestion
    BAM-25900Windows-based Docker image for atlassian/bamboo-agent-base
  27. Suggestion
    BAM-19731Add Capability for 'Docker Runner' to connect to private image registry
  28. Suggestion
    BAM-26108Enable Logging of Login/Logout Events in Bamboo
  29. Suggestion
    BAM-26114Bamboo Automatic offline agent removal to consider number of offline days
  30. Suggestion
    BAM-26125Introduce project/plan scoping to specs encryptions
  31. Suggestion
    BAM-15464Provide HTTP(S) authentication method option for Bitbucket Server type repository
  32. Suggestion
    BAM-20208Add support for Amazon Aurora Database
  33. Suggestion
    BAM-21321Change default running environment to Docker container instead of Agent environment
  34. Suggestion
    BAM-18273Ability to bulk update Bitbucket Server/Stash repository URLs
  35. Suggestion
    BAM-25769Deleted tag in Bitbucket server still present under packed-ref folder post Source code checkout in Bamboo Server
  36. Suggestion
    BAM-17063Allow prioritisation of jobs within a build plan
  37. Suggestion
    BAM-20107REST API to enable/disable Triggers
  38. Suggestion
    BAM-25891Add REST API to get plan repositories
  39. Suggestion
    BAM-1223Import Export individual projects / plans
  40. Suggestion
    BAM-15896Automatically rollback to previous successful deployment if the current fails
  41. Suggestion
    BAM-18297Bamboo make the Restricted Administrator role configurable
  42. Suggestion
    BAM-19898Plans braches using multiple repositories could automatically checkout them using the same source branch name
  43. Suggestion
    BAM-20460Allow Repository-Stored Specs to be scanned from branches
  44. Suggestion
    BAM-20680Support Repository Tag task at Specs YAML
  45. Suggestion
    BAM-20951Allow configuring default volumes for Docker Runner
  46. Suggestion
    BAM-21313Add option to enabe and disable task, jobs and plans using YAML Specs
  47. Suggestion
    BAM-21384Source Control tasks
  48. Suggestion
    BAM-6328Clean working directory only after each successful build
  49. Suggestion
    BAM-12063Improve the way Remote Agents work in DHCP networks
  50. Suggestion
    BAM-12522Allow JIRA to be configured as an Avatar server
Refresh results
1 of 1566
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20915

GitHub repository type doesn't work with anything other than username/password

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Repository (Github)
    • None
    • 1
    • 4

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

      The GitHub repository configuration doesn't have the option to use any other authentication method other than Username and Password.

      Add the functionality to use SSH keys to authenticate in GitHub.

          Form Name

            There are no comments yet on this issue.

              Unassigned Unassigned
              gluz2@atlassian.com Guilherme Luz (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: