|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
yeah, the use case is pretty simple: I'd like to be able to post a comment to the issue which relates to my Git branch or pull request. Given a command with jenkins variable expansion it would be easy to post a useful comment, however I guess the tricky part is figuring out the issue to post the comment to. Maybe best, one could provide a string (with jenkins variable expansion) that the plugin could parse for the issue ID.
We are using branch names for the implementation of certain tickets, e.g. feature/PR-X-something - whereas PR-X is the youtrack issue ID, thus there is no leading #. Mentioning that, from the documentation it was not clear to me that it requires the leading # for parsing ticket IDs from commit messages, so maybe that's something you could clarify in the docs also.