Let us go through recent updates from the @atlassian ecosystem #ParentChildPipelines #PRID #TaskID #int64 #Analytics #Teams #HomeDashboards
Introducing parent/child pipelines
Bitbucket Pipelines now supports parent/child pipelines, enabling modular and streamlined workflows. This lets you trigger nested pipelines for better organization and enhanced parallelism.
Link(s): Introducing parent child pipelines
REST API change: Pull request comment and task IDs will be expanded to 64-bit integers
Starting 18 Aug 2025, Bitbucket Cloud REST API will update pull request comment and task IDs from int32 to int64. Make sure your integrations can handle 64-bit integers to avoid issues.
Link(s): REST API change: Pull request comment
Teams data available for data shares
Exciting news! Atlassian has added two new tables—atlassian_team and atlassian_team_member—to your data shares, enabling seamless connection of Jira issue data with team info using Team ID. These updates require no action and are already live. Use them to enhance reporting and filtering in your tools.
Link(s): Teams data available
New features released for Home Dashboards beta!
The Home Dashboards beta just got better! Now explore Dashboard Insights, Smart Link widgets, and Live Drilldowns to get faster insights and take quick action. You can also report on Jira Service Management SLAs and request types. More features like single value charts and chart filters are coming soon!
Link(s): New features released for Home Dashboards beta!
Upcoming Event:
ACE Hyderabad event with Test Triangle
Aug 8, 5:30 – 8:30 PM (GMT+5:30), Hyderabad
Listen from the Atlassian experts at Test Triangle on the latest topics and trends in the Atlassian ecoysystem.
Link(s): Atlassian Hyderabad presents Ace hyderabad event
Blog(s) of the week :
Explore the key differences between Jira Data Center Automation Rules and ScriptRunner, from a seasoned consultant’s perspective. Learn when to use native automation and when ScriptRunner offers more power and flexibility. A must-read for teams optimizing large-scale Jira environments.
Link(s): Jira Data Center: Automation Rules vs. ScriptRunner
Video(s) of the week:
Reopening old closed bugs in Jira can disrupt workflow and confuse team priorities.These bugs were likely closed after thorough testing, so reviving them may duplicate effort or ignore current project context. Old issues might not align with the current codebase or business logic, leading to wasted time.
Link(s): Reopening old bugs
