What are best practices for bugs/features submissions when integrated with BitBucket and Jira?

[L Jones]

How do I get transparency on previous and existing tasks from Jira to BitBucket on a side panel that team members can filter?

Do developers need to have another window to see assigned tasks or alternate?

[Aron Gombas _Midori_]

Jira work items can be seen in various forms on the Bitbucket UI. It requires that you connect your Bitbucket workspace to your Jira Cloud site, and eventually that you reference the work items from commit messages, pull request titles and such.

I think the mid part titled "Plan and track projects right from within Bitbucket" here is a good entry point to learn more: https://www.atlassian.com/software/jira/bitbucket-integration

Note that they use pretty old screenshots there, but you should be able to find the corresponding parts on the new navigation.

[L Jones]

After searching through several pages on whether DVCS accounts are still used with Jira-BitBucket integrations, which is the right manage app screen, and Use Jira Cloud projects in Bitbucket Cloud, I found the answer. You have to

• Add the Jira integration with BitBucket: Make sure it is connected to the right site under the Admin site settings: https://admin.atlassian.com/
• Add BitBucket on Jira: https://bitbucket.org/product/features/pipelines/integrations and also the directions below
  • Ensure it is showing in your BitBucket project settings under Atlassian integrations > Jira.
• Make sure users have appropriate access to it from the admin apps panel for the application and site. It might work for admins, but users might not see it unless switched over.
  
  After an integration, on the left side panel will show an item called Jira work items. It looks like this:

In the center or top right, add a manual link project from the drop down, after that, the issue tracking shows back up. You just follow the steps of selecting the Jira project to it and he issue tracking returns. You just need to remember to add the TODO in your source code to easily link it with the Jira bug, feature, or task.

It took me an hour, but with these directions, it could be done in 10 to 30 minutes.