-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Bitbucket Cloud: Add Start Work Support #4047
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
area-integrations
Issues or features related to integrations
integration-bitbucket
Issues or features related to Bitbucket integrations
verified ✔
Verified
Milestone
Comments
This was referenced Feb 12, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 27, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 27, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 27, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 27, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 27, 2025
I've attached the cases that are needed to be checked in this ticket (it's in the description). Do you have any thoughts about what else should be tested regarding the issues? |
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
7 tasks
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Feb 28, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 3, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 3, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 3, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 4, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 4, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 4, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 4, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 4, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
sergeibbb
added a commit
that referenced
this issue
Mar 5, 2025
saeedzaha
pushed a commit
to saeedzaha/vscode-gitlens
that referenced
this issue
Apr 28, 2025
saeedzaha
pushed a commit
to saeedzaha/vscode-gitlens
that referenced
this issue
Apr 28, 2025
saeedzaha
pushed a commit
to saeedzaha/vscode-gitlens
that referenced
this issue
Apr 28, 2025
saeedzaha
pushed a commit
to saeedzaha/vscode-gitlens
that referenced
this issue
Apr 28, 2025
saeedzaha
pushed a commit
to saeedzaha/vscode-gitlens
that referenced
this issue
Apr 28, 2025
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-integrations
Issues or features related to integrations
integration-bitbucket
Issues or features related to Bitbucket integrations
verified ✔
Verified
Add support for seeing Bitbucket issues in Start Work.
Also make sure Bitbucket issues can be associated to branches using the "associate issue to branch" command in branch context menus.
Make sure that the associated issue is displayed on Home
Make sure the associated issue is displayed on Graph
(parent #3916, related (azure) #3979)
Testing notes
select issue on StartWork and create a branch
associate issue to branch using context menus


see the associated issue on Home (current and recent)
see the associated issue on Graph
The text was updated successfully, but these errors were encountered: