Currently, bedevere adds a convenient link to issue gh-NNNNN to the first message of a PR that includes gh-NNNNN in the title when the PR is created:

However, if you look at the corresponding issue, the link to the PR is lost in the issue timeline among comments, metadata changes, and mentions from other issues and PRs:
Click to see an excerpt of the issue timeline

The only way to find related PRs is to scroll through the whole issue history looking for mentions, and figure out which of these are PRs that solve the issue.
When a PR that includes gh-NNNNN in the title is created bedevere should:
- add a link to the issue in the first message of the PR (this already works)
- add a link to the PR in the first message of the issue
If more PRs that include the same gh-NNNNN are created (e.g. backports), the list of PRs in the first message of the issue should be updated accordingly. This will provide an easy way to track all related PRs.
About the implementation:
- only PRs that include the issue in the title should be added to the list
- PRs/issues that simply mention this issue in comments could be added to separate lists, but that's out of the scope of this issue
- the PRs could be listed using a checklist (or even better, the upcoming improved tasklists)
- a short notice (possibly with a link) could be added to clarify that the the list wasn't added by the OP, but by
bedevere
- this could replace the messages that
bedevere adds when backport PRs are created
Currently,

bedevereadds a convenient link to issuegh-NNNNNto the first message of a PR that includesgh-NNNNNin the title when the PR is created:However, if you look at the corresponding issue, the link to the PR is lost in the issue timeline among comments, metadata changes, and mentions from other issues and PRs:
Click to see an excerpt of the issue timeline
The only way to find related PRs is to scroll through the whole issue history looking for mentions, and figure out which of these are PRs that solve the issue.
When a PR that includes
gh-NNNNNin the title is createdbedevereshould:If more PRs that include the same
gh-NNNNNare created (e.g. backports), the list of PRs in the first message of the issue should be updated accordingly. This will provide an easy way to track all related PRs.About the implementation:
bedeverebedevereadds when backport PRs are created