Add Row

Add Element

update

[Company Name]

update

Add Element

Home
Categories

Welcome To Our Blog!

Click Subscribe To Get Access To The Industries Latest Tips, Trends And Special Offers.

All Posts
Agile Training
SAFe
Agile
DevOps
Product Management
Agile Roles
Agile Testing
SRE
OKRs
Agile Coaching
OCM
Transformations
Testing
Developers
Product Owners
Scrum Masters
Scaling Frameworks
LeSS
Cultural Foundations
Case Studies
Metrics That Matter
Agile-DevOps Synergy
Leadership Spotlights
Team Playbooks
Agile - vs - Traditional

September 12.2025

2 Minutes Read

API Tokens Enhance Security: Transitioning from App Passwords in Bitbucket

Abstract green digital landscape with branching lines and code symbolizing Bitbucket API tokens transition.

The Shift from App Passwords to API Tokens: What Developers Need to Know

The realm of software development is ever-changing, and security is at the forefront of these changes. With the recent announcement by Atlassian regarding the deprecation of app passwords in Bitbucket Cloud, developers must adapt to a more secure authentication method using API tokens.

Understanding the Transition Timeline and Its Implications

As of September 9, 2025, Bitbucket Cloud will halt the creation of new app passwords, marking a significant turning point in how developers manage authentication. Existing app passwords will remain valid until June 9, 2026, allowing users a transition period to migrate their integrations to API tokens.

Current integrations will not face interruptions during this phase, but as new integrations are created, API tokens will become the only viable option. To facilitate this transition, developers are encouraged to start using API tokens for their projects sooner rather than later to avoid last-minute disruptions as the final deprecation phase approaches.

Benefits of API Tokens Over App Passwords

What makes API tokens a better option than the traditional app passwords? Firstly, API tokens bring enhanced security features—including expiration controls, which allow developers to set limits on how long a token remains active. This greatly reduces the risk associated with exposure in case of a security breach. Moreover, API tokens are managed through a centralized system, providing better oversight and control for administrators.

Preparing for Future Phases: Best Practices for Developers

For administrators and teams that currently rely on app passwords, it’s crucial to take proactive steps toward migration. Encourage your teams to start employing API tokens now to ensure a smooth transition. This proactive approach safeguards against potential disruptions when all app passwords become invalid in June 2026.

Additional Resources and Support

Atlassian emphasizes their commitment to assisting users through this transition. Developers can easily create API tokens by navigating to their account settings. By doing so, they can ensure that their applications remain functional and secure, embracing the modern authentication practices laid out by Atlassian.

Team Playbooks

187 Views

0 Comments

Write A Comment

Related Posts All Posts

02.20.2026

How Datasite Achieved Agile Collaboration by Cutting Meetings with Loom

Update Redefining Workplace CollaborationIn the modern workplace, the challenge of maintaining productivity amidst a flurry of meetings is a familiar battle, and Datasite has discovered an innovative solution. By integrating video communications with project management tools, Datasite has managed to cut more than 4,000 meetings in just five months, achieving significant time savings and enhancing workplace culture.At Datasite, the implementation of tools such as Loom, Jira, and Confluence has created a new paradigm for communication. Traditionally, the company's reliance on meetings blurred the lines between productivity and time-consuming discussions, leading to overlapping schedules and diminished focus. However, with the introduction of asynchronous video updates, employees were empowered to share project updates and collaborate without the constraints of scheduled meetings.Embracing Time EmpathyOne of the remarkable shifts at Datasite is the cultural transformation towards 'time empathy', as described by JR Harrell, EVP of Product Operations and Enablement. This cultural ethos encourages teams to prioritize asynchronous communication, allowing them to communicate effectively while preserving time for deep work. This shift not only alleviates the clutter of meetings but also promotes a healthier work-life balance.The benefits are tangible; with over $500,000 reclaimed in lost meeting time, employees can now engage in more meaningful and impactful work, fostering both innovation and efficiency.The Power of IntegrationThe seamless integration of Loom with Jira further enhances project clarity and collaboration. Teams can now provide context through video explanations directly within Jira tasks, allowing colleagues to grasp complex concepts without unnecessary delays. Asynchronous tools like Loom have also shown to expedite bug resolutions and project updates by adding rich, visual information that enhances understanding in a fraction of the time a traditional meeting would take.As organizations continue to adapt to hybrid work environments, leveraging tools that reduce meeting fatigue and enhance clarity will be essential. The successful transition at Datasite serves as a compelling case for others grappling with similar issues in maintaining productivity across dispersed teams.

02.19.2026

Unlocking Efficiency: New Event Triggers in Bitbucket CI/CD Workflows

Update Revolutionizing CI/CD with New Event Triggers In a digital landscape where speed and precision are paramount, Atlassian's Bitbucket has recently unveiled new event-based triggers for its CI/CD pipeline that aim to streamline development processes and enhance efficiency. These updates, introduced on February 17, 2026, are poised to transform the way development teams manage and respond to pull requests and deployment activities. What are Event-Based Triggers? The new trigger types allow teams to execute custom pipelines based on key events, such as the successful completion of a prior pipeline or a significant update to a pull request. This paves the way for complex workflows, promoting better automation and reducing the manual oversight traditionally required in deployment cycles. Significant New Trigger Types The introduction of six new trigger types is a game changer for developers. These triggers include: pipeline-completed: Activates upon the completion of any pipeline, be it successful or failed. deployment-completed: Triggers when a deployment concludes. pullrequest-created: Initiates a custom pipeline when a new pull request is established. pullrequest-updated: Fires when any changes are made to an existing pull request. pullrequest-rejected: Executes upon the rejection of a pull request. pullrequest-fulfilled: Runs actions once a pull request is successfully merged. The Benefits of Enhanced Automation These new triggers allow for a much tighter coupling between CI/CD processes. By ensuring that further actions depend on the outcomes of previous ones, teams can build comprehensive workflows that maintain high-quality standards. For example, developers can automate the testing and alerting processes based on specific pull request events, which caters directly to quality assurance and boosts productivity. Real-World Implications For organizations embracing Agile methodologies, these streamlined processes align perfectly with the Agile Playbook's principles, enhancing responsiveness to changes and customer needs. By decreasing the number of manual checks and configurations required, development teams can deliver features faster and more reliably. Conclusion: Automation as the Future of Development As the tech community continues to embrace automation, the introduction of these event triggers in Bitbucket serves as a testament to the ongoing evolution of CI/CD workflows. By capitalizing on these triggers, development teams can not only enhance their efficiency but also stay competitive in an ever-evolving industry.

02.15.2026

Transforming AI Theater Into Results: The Path to AI Fluency

Update Understanding AI Theater and Its Impact on ProductivityAs artificial intelligence (AI) continues to amplify its presence across industries, organizations face a growing dichotomy between merely using AI and achieving genuine AI fluency. The term "AI theater" describes the flashy demonstrations and superficial enthusiasm surrounding AI deployment that often fail to deliver impactful results. Many teams fall into patterns such as "tool tourism"—where they collect various tools without integrating them into their workflows—leading to an illusion of progress without real outcomes.Embracing AI Fluency for Meaningful ChangeIn contrast, AI fluency represents a deeper understanding and application of AI within organizational contexts. It’s not just about using AI to execute tasks, but about fostering a collaborative approach that encourages creativity and critical thinking. AI fluent teams excel by asking insightful questions that emphasize reasoning and analysis over rote tasks, thereby unlocking significant productivity gains. By promoting an environment of experimentation, teams can transform setbacks into opportunities for growth, realizing the full potential that AI can offer.The Role of Leadership in Driving AI SuccessFor leaders, the challenge lies in shifting from superficial engagement with AI to fostering an organization's collective fluency. This requires providing clear guidance that encourages exploration while building the confidence of teams to leverage AI effectively. Insights from product leaders reveal that success does not stem from merely acquiring tools but from creating a culture where AI fluency flourishes. As teams experiment and learn from AI, they can evolve past mere usage into roles as critical thinkers and innovators.Moving Beyond AI Theater: Key Steps to Enhance AI FluencyTo overcome AI theater obstacles, leaders need to focus on three core principles: embracing constraints over rigid processes, developing AI-shaped problem-solving skills, and prioritizing judgment over immediate infrastructure. These steps equip teams with the ability to tackle complex challenges rather than simply performing tasks faster. Understanding these principles is crucial in cultivating an adaptive and fluid workforce that thrives amid evolving AI landscapes.The Future of Work with AI FluencyAs the landscape of employment adapts to the rising prevalence of AI technologies, the real measure of success will be grounded in fluency—understanding when to use AI and when to rely on human insight. As more teams embrace these concepts, we will see a distinct divide between those who merely adopt AI as a tool and those who seamlessly integrate it into a creative and multifaceted problem-solving approach. The future of work not only hinges on technical skills but on the ability to foster innovation through AI fluency.

API Tokens Enhance Security: Transitioning from App Passwords in Bitbucket

The Shift from App Passwords to API Tokens: What Developers Need to Know

Understanding the Transition Timeline and Its Implications

Benefits of API Tokens Over App Passwords

Preparing for Future Phases: Best Practices for Developers

Additional Resources and Support

Terms of Service

Privacy Policy

Core Modal Title