Thankfully you actually don't have to attribute the PR to one specific issue. You could just mention in the git summary that it's related to the pull request but doesn't necessarily have to close the issue. I'd be happy to help. For example, within those tickets that are partially influenced by the commit, You could tell me to close the ticket and create a different one with the more accurate and pinpointed summary etc....realthunder wrote: ↑Thu Feb 27, 2020 3:25 am I am going through the Expression issue tracker, and find it hard to pinpoint exactly which commit to attribute for solving the issue. And many tickets actually involve multiple issues, that are either resolved, or only partially resolved. Any suggestion on what I shall do with those tickets?
To be clear, what I mean is within the git summary you can type: issue #2220, #4321, #4322,
And mantis will associate the PR with that ticket. (Those are fictitious issues btw). It won't close those tickets unless you write:
closes #2220, #4321, #4322
The tickets you choose to associate (not close} with the PR we can then drill down in to and see if it's worth keeping them open or closing them in favor of a more nuanced issues (since part of it was addressed by the PR)