I’ve got Jenkins set up with the JIRA plugin and everything works fine. The problem is when developers commit their code to SVN, the commit messages show up in JIRA tickets but they all appear to come from the same Jenkins service account.
Is there a way to make these automated comments appear under the actual developer’s name who made the commit? Right now it just shows as one generic user for all Jenkins-generated updates.
I want the JIRA integration to preserve the original author information from the SVN commits instead of using a single system account for everything.
You’re right about the mapping issue, but there’s another config step people miss all the time. Check that your Jenkins JIRA plugin uses “Author” not “Committer” in the SCM settings. This matters because Jenkins might grab the wrong identity field from SVN. Also make sure your JIRA instance lets the Jenkins service account act on behalf of other users - you need specific application link permissions in JIRA’s admin settings. I’ve seen setups where everything looked perfect but the permission model blocked author attribution. Test with one commit first to make sure the mapping works before rolling it out to everyone.
Had this exact problem two years ago. You need to configure the JIRA plugin to map SVN commit authors to JIRA users correctly. Go to your Jenkins job config, find the JIRA plugin settings, and enable “Use SCM author” (or whatever it’s called there). But here’s the tricky part - your SVN usernames have to match JIRA usernames exactly. If they don’t match, create a user mapping file so Jenkins knows how to translate SVN authors to JIRA users. Also check that your Jenkins service account can post comments on behalf of other users in JIRA. Without that permission, it’ll just use the service account name no matter what you configure.
totally get it, it’s frustrating! you should look for an option in the jira plugin settings of jenkins to “use commit author”. it’s usually in the advanced section. also, double-check that your svn usernames are the same as your jira ones; otherwise, it won’t link correctly.