Git branch to bug linking doesn't work via commit message tagging for projects in a project group
Bug #1629433 reported by
Jeff Lane
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
Reading this announcement:
http://
Says we can add the text LP: #XXX to a commit message to link that branch to an LP bug automatically.
I tried this with a commit message that looked like this:
"Precheck now verifies existing SID entries and allows for changing them if they're incorrect LP: #1629071"
However, this did not result in my branch being linked to the bug.
I WAS able to link it manually from the LP web UI on the Merge Request, so all's well that end's well, but it would be nice for the commit message tagging to work.
Related branches
lp:~cjwatson/launchpad/git-update-related-bugs-more-permissions
- William Grant: Approve (code)
-
Diff: 40 lines (+6/-1)2 files modifieddatabase/schema/security.cfg (+3/-0)
lib/lp/code/model/tests/test_branchmergeproposaljobs.py (+3/-1)
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| tags: | added: code-review git lp-code trivial |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in launchpad: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| status: | Triaged → In Progress |
| summary: |
- Git branch to bug linking doesn't work via commit message tagging + Git branch to bug linking doesn't work via commit message tagging for + projects in a project group |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #3 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks for your report. This is due to OOPS-a8d71d23141d75b094be9a3d29a1be0c: "permission denied for relation project", so it'll be a simple security.cfg fix along with working out an appropriate test.