Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Don't match every Jira issue found in PR description
See original GitHub issue(continuing from https://github.com/atlassian/github-for-jira/issues/119#issuecomment-1010360037)
Recently you released a feature where a Jira issue ID like TEST-12 can be included in the description of a PR and automatically linked to the issue.
This is great, but it’s common to refer to multiple tickets within the description of a PR, and the PR itself only be associated with one Jira ticket.
Personally, I would only expect a PR to be linked to a Jira issue if it matched something like fixes [TEST-12] or closes [TEST-12]. A special keyword would ideally be required before the issue ID, and the issue ID be “linked” i.e. wrapped with [ and ].
Any chances you could refine this feature to provide more control over this linking?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:21
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Would it be possible to enable customers to enable/disable each type of automatic linking? We’re also experiencing tickets resolving/closing unexpectedly due to their mention in a PR body or linking in a review. It seems like enabling granular control of the linking capability would be a simple way to satisfy most customer needs.
It’s a very common use case to include an “out of scope” section in a Pull Request description to indicate tickets that were not fixed in the PR.
This new functionality is causing out-of-scope tickets to be linked to PRs and then automatically moved to “done” based on our automations when the PR merges.
It would be very nice to be able to toggle off this functionality or set an explicit pattern that picks up only certain tickets linked in a Pull Request description.