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-13625JBAM - Jira Bamboo plugin does not handle project key rename in JIRA
  2. Suggestion
    BAM-26170Allow group aggregation for users created by JIT provisioning
  3. Suggestion
    BAM-26171Disable local password reset for JIT provisioned users
  4. Suggestion
    BAM-20107REST API to enable/disable Triggers
  5. Suggestion
    BAM-26173Support for custom headers in webhook notifications via UI and YAML Specs
  6. Suggestion
    BAM-26172REST API endpoint for managing webhook templates
  7. Suggestion
    BAM-26168Allow Bamboo to use multiple Jira instances
  8. Suggestion
    BAM-26156Bitbucket Cloud integration support after deprecation of app password
  9. Suggestion
    BAM-1223Import Export individual projects / plans
  10. Suggestion
    BAM-21370Bamboo with Oracle 19c multitenant mode support
  11. Suggestion
    BAM-21372Improve our Bamboo docker hub readme
  12. Suggestion
    BAM-13165Make build expiry configurable at branch level
  13. 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.
  14. Suggestion
    BAM-20754Support for Queue Priority Plugin
  15. Suggestion
    BAM-25537Running Bamboo Ephemeral agents on different Kubernetes clusters
  16. Suggestion
    BAM-21410Make overriding of the entrypoint the default behaviour of docker runner
  17. Suggestion
    BAM-26162Regenerate SSH keys automatically from Bamboo for Bitbucket linked repositories with Expiry option set at Bitbucket DC
  18. Suggestion
    BAM-5251Generate a report on build agent utilization.
  19. Suggestion
    BAM-20959Support for Podman as a container platform
  20. Suggestion
    BAM-14525Better support for creating releases from branch
  21. Suggestion
    BAM-18412Suppress first build action when publishing from Bamboo Specs
  22. Suggestion
    BAM-20472Allow to add capabilities to Elastic Agents using bamboo-capabilities.properties file
  23. Suggestion
    BAM-20134Low performance on deleting plan branches (big AUDIT_LOG table)
  24. Suggestion
    BAM-20497Allow nested sequences of tasks to work in YAML Specs
  25. Suggestion
    BAM-25441Allow option in Bamboo GUI to rename username for Bamboo Internal directory users
  26. Suggestion
    BAM-25797Provide option in Bamboo for multiple remote agents to share a common Build working directory
  27. Suggestion
    BAM-25891Add REST API to get plan repositories
  28. Suggestion
    BAM-25929Ability to have the Websudo functionality working with SAML / SSO
  29. Suggestion
    BAM-21066Allow overriding branches for non default repositories in YML specs
  30. Suggestion
    BAM-25993Create REST API to retrieve Plans by using Quick Filter
  31. Suggestion
    BAM-25992Create REST API to retrieve Plans by label
  32. Suggestion
    BAM-22465Enhance Bitbucket Cloud repository integration in Bamboo to include support for BBC Access Tokens
  33. Suggestion
    BAM-25761Enhance Bitbucket Cloud and Bamboo integration to allow project access tokens
  34. Suggestion
    BAM-17728Get last timestamp users authenticated in Bamboo and from where
  35. Suggestion
    BAM-20737Leverage Git servers that enable allowReachableSha1InWant for custom builds instead of always doing a full fetch
  36. Suggestion
    BAM-25955Possibility to manage capabilities for Elastic Images via REST API
  37. Suggestion
    BAM-20065Integrate Bamboo (Server) Notification on Slack
  38. Suggestion
    BAM-21632Allow project-level repositories using RSS to publish deployment projects
  39. Suggestion
    BAM-25660Make Bamboo more resilient to network/database failures
  40. Suggestion
    BAM-26139Enhance permissions model in Specs
  41. Suggestion
    BAM-20915GitHub repository type doesn't work with anything other than username/password
  42. Suggestion
    BAM-21356Have the ablitiy to listen to tags for Bamboo specs.
  43. Suggestion
    BAM-20962Explicitly revoke global permissions (i.e. Create Plan) on a project level
  44. Suggestion
    BAM-21361Allow for tag detection on non-default Bitbucket repositories.
  45. Suggestion
    BAM-21376Improve the Azure DevOps integration with Bamboo
  46. Suggestion
    BAM-18273Ability to bulk update Bitbucket Server/Stash repository URLs
  47. Suggestion
    BAM-20475Allow to configure project to mark by default the option "Clean working directory after each build"
  48. Suggestion
    BAM-17917Add user credentials to Docker Build task
  49. Suggestion
    BAM-16507Disable concurrent logins by same user
  50. Suggestion
    BAM-19825Branch regular expression filter for automatic PR detection
Refresh results
1 2 3 4 5Next >>
1 of 1612
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13625

JBAM - Jira Bamboo plugin does not handle project key rename in JIRA

Log In
Not Being Considered
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • JIRA integration
    • None
    • 0
    • 7
    • 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.

      After project key rename information about past builds for issue/project performed for old issue key/project key is not visible. It seems JIRA Bamboo plugin cannot handle project key renames.

      More information:
      This problem relates to issue keys parsed from commit messages and stored in Bamboo against build results. We have no information about Jira notifying connected applications about project key rename, thus Bamboo doesn't have a chance to act upon this.

        is duplicated by

        JDEV-23945 Loading...

              • All
              • Comments
              • Work Log
              • History
              • Activity

              Krystian Brazulewicz added a comment - 30/Jul/2019 10:11 AM
              Atlassian Update

              Hi everyone,

              Thank you for your interest in this issue.

              While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future.

              We'll typically review this request in about 6 months time, at which point we’ll consider whether we need to alter its status.

              We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:

              1. Robustness of Plan Branches
              2. Performance and stability improvements
              3. Providing building blocks for High Availability and Disaster Recovery solutions
              4. Improving permission system
              5. Allowing per-project allocation of resources
              6. Improving Bitbucket Server and Jira integrations

              We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

              To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

              Kind regards,
              Bamboo Team

              Krystian Brazulewicz added a comment - 30/Jul/2019 10:11 AM Atlassian Update Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. We'll typically review this request in about 6 months time, at which point we’ll consider whether we need to alter its status. We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including: Robustness of Plan Branches Performance and stability improvements Providing building blocks for High Availability and Disaster Recovery solutions Improving permission system Allowing per-project allocation of resources Improving Bitbucket Server and Jira integrations We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Bamboo Team

                Unassigned Unassigned
                mkujalowicz Michal Kujalowicz
                Votes:
                5 Vote for this issue
                Watchers:
                12 Start watching this issue

                  Created:
                  16/Aug/2013 9:39 AM
                  Updated:
                  2 hours ago
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian