Currently as soon as the plugin sees a new issue key, it assumes it's a new operation on a new issue, so it stops processing the comment. This can cause a comment to appear cut off if the user wanted to say something like "Fixed this issue, which was also causing TEST-24 because of..." where currently the comment will end up "Fixed this issue, which was also causing". The intent here is to allow multiple operations on multiple issues in the same line, but if there are no commands after an issue key, there's no sense in behaving this way.
So, the proposal:
TEST-1 #comment fixed this and TEST-2 together
Would leave comment "fixed this and TEST-2 together" on TEST-1 and do nothing to TEST-2.
TEST-1 #comment fixed TEST-2 #done
Would retain the behavior of leaving the comment "fixed" on TEST-1 and transitioning TEST-2 to Done.
Currently as soon as the plugin sees a new issue key, it assumes it's a new operation on a new issue, so it stops processing the comment. This can cause a comment to appear cut off if the user wanted to say something like "Fixed this issue, which was also causing TEST-24 because of..." where currently the comment will end up "Fixed this issue, which was also causing". The intent here is to allow multiple operations on multiple issues in the same line, but if there are no commands after an issue key, there's no sense in behaving this way.
So, the proposal:
Would leave comment "fixed this and TEST-2 together" on TEST-1 and do nothing to TEST-2.
Would retain the behavior of leaving the comment "fixed" on TEST-1 and transitioning TEST-2 to Done.