mozilla-services / mozilla-services/updatebot
Carry forward blocks/deps when closing a bug as a duplicate.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We closed https://bugzilla.mozilla.org/show_bug.cgi?id=1721002 as a duplicate of the (newly filed) https://bugzilla.mozilla.org/show_bug.cgi?id=1724595 because 1721002 was older and a new update had become available. That worked as expected.
However 1721002 had bug dependencies that were lost when we closed it as a dupe. We should look for any (open) dependencies or (open) blockers and copy them into the new bug we file.
Sometimes bugzilla will error if we try to create some sort of loop in deps/blockers - we shouldn't hit that because it's a brand new bug but just to be safe we should do this operation in a separate try/catch block, and if it fails, file a comment on the bug about what we tried to do.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Bugzilla duplicate-closing flow for the bugs linked in the issue, then inspect how dependencies and blockers are read and written. Done means open relationships are copied to the newly filed duplicate, while loop errors are isolated and reported as a comment on the bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100