Search for a command to run...
Track each code change to the ticket it was requested by
Creating apps built with ❤️ using Oracle APEX. PL/SQL dev. Exploring the AI and ML world. Keen on front-end, visual arts and new technologies. Love travel, sports, photography.
No comments yet. Be the first to comment.
Impressions from APEX Alpe Adria 2026
The Use Case Oracle APEX has a special template for Dialog Pages, called Drawer. This template is also available for any Region on you Page (this time called Inline Drawer). 💡 A Drawer is an overlay
The Use case (and the issue) What you see on this screenshot is a pretty common requirement in an APEX application - A form, where you have some text item or dropdown menu, followed by a button or som
The power of Claude Code - offline, free, secure
Using a REST Media Resource as an image source
In the world of software development, managing code changes and tracking project progress are two important aspects of the whole process. To improve the visibility and traceability of all changes, and most importantly see which code changes have been made to handle which specific Jira ticket, integrating Bitbucket with Jira is a very good idea. And speaking in general - integrating your version control tools and your ticketing system.
In the case with Bitbucket and Jira it is a lot easier, since both tools are owned by Atlassian. This integration allows developers to link their code commits, branches, and pull requests directly to Jira tickets. Here’s how this connectivity will benefit you and your team:
🔸 Easy to keep track - you can see exactly which code changes go with which project task. Just add the ticket number when you commit your code, and it links up automatically to the Jira task.
🔸 Updates in real time - as you push changes or merge code, Jira updates itself. So, if you finish a task, the ticket might close itself, or if there's a comment in Bitbucket, it shows up in Jira.
🔸 You can clearly see why certain code changes were made by looking at the linked Jira task.
🔸 Save time - instead of hopping between apps, you handle tasks and code in one place. It cuts down the unnecessary job of switching tabs or programs.
Open Bitbucket and select the Settings / Workspace Settings
Select the Jira menu item from on the left
You will see the Jira integration screen. Listed are all Jira sites to which you have access with the currently logged in user. To connect Bitbucket and Jira, click on the Connect button. In the popup window that will open, click on Grant access button. Note that you need to be an Administrator to complete the setup. Otherwise, ask you Admin to approve the step
Jira issues menu item. You should now see the issue from your Jira board.
If you don’t see any Jira issues yet, you might need to check which Jira Projects have been linked to Bitbucket. To do so, click on the icon in the top right corner (a folder and a link icon). Then pick Manage linked projects. In the modal window that will open, select the Jira Projects you need to get linked and click on the Link project button. Once done, all issues of the selected Jira projects will appear on the page.
To get a better idea of what this integration really means, let’s look at one basic example. We will first create a Jira ticket for a new feature. Once created, we will use the ticket number to create a new branch in our source control system (Bitbucket). On the next step we will do some code changes and commit them to the code repository. The result will be that the Jira ticket will get updated automatically and we will be able to trace the code changes to the ticket they were requested with.
git checkout -b APX-6-<branch-name> when creating new branch and git commit -m “APX-6 <commit message>“ when doing a commit.Create a new Jira ticket. For this example, my ticket ID is APX-6.
Once the ticket is created, take a look at the Development section of the Details on the right. There are two new options there - Create branch and Create commit. They can suggest you how to create a new branch, using the Ticket ID or how to make a commit to a branch using the Ticket ID. Take a look at the example below.
Create branch provides the option to configure the default branch name format used by the suggestions.Next step is the actual development. For this demo I have created a new branch using the suggested command from Jira: git checkout -b APX-6-create-samples-table
I have added a new file in my new branch APX-6-create-samples-table (demo_users.sql) and committed the changes using the suggested command: git commit -m “APX-6 New demo table created.“. What you’ll see now in your Jira Board is the integration in action. Next to the user icon, there is a new tiny icon, indicating that there is a new commit in the related Bitbucket repository.
You can click on the Jira Ticket and explore the full details. You can notice that the Development section in Details is now showing the number of related Bitbucket branches and commits.
You also have the option to Create a Pull request for the associated branch. The cool thing about this feature is that you get redirected to Bitbucket with all the necessary information about the Pull request pre-filled. This includes auto-generated Description, which consists of all comments about the existing commits in ascending order.
Enjoy your new setup! I’m sure it will make your life as a developer easier and will give you that level of traceability and automation that can speed up the development process.
Did you like this blog post? Follow me! 🔔
