Direct Message notifications slack

[grumpasaurus]

So far all the add-ons that I've found only support notifications sent to a pre-set channel in Slack.  

Is there any plugin where, in lieu of an email, send a direct message as a pre-set User/Bot directly to someone?  This would be useful when doing @ mentions directly at people.

[Kelly Schoenhofen · Accepted solution]

I think I figured it out - I had another user with my email address, and once I changed that to something else (so the "right" user - the one Jira knew - now was the only person with that email address) smart commits started working.

I don't want to dig in and reproduce it, but I also saw an issue with case sensitivity in Stash/Fisheye - two authors show up if you have the same email address with mixed case. Oddly enough, both had the same Gravatar avatar, so somewhere it's calling Gravatar with just one case.

If you use Crowd to connect to AD, you get the option to convert everyone to lower case, but you don't get that option if you use Jira to connect to AD, and then have Stash & Fisheye use Jira as their user server.

[Kelly Schoenhofen]

Any ideas? Should I open up a support ticket?

[Kelly Schoenhofen]

I created a custom security scheme with "anyone" set to every permission (including adminster project) to try to rule out a security issue for Fisheye to be kept getting told there's no issue with that name; it made no difference that I could see.

Leaving everything else the same, I tried the Crucible integration. Crucible seems to be fine - if I commit with:

git commit -m "ATP-7 #comment next try +review @username"

Fisheye logs this:

2012-12-04 15:15:16,821 WARN [CommitNotifier1 ] com.atlassian.fecru.plugin.commithook.jira.commands.CommandHandler CommandHandler-doForEachIssue - No issue with key 'ATP-7' found in any configured JIRA servers

2012-12-04 15:15:16,910 DEBUG [CommitNotifier1 ] net.java.ao.sql DatabaseProvider$LoggingSqlListener-onSql - SELECT * FROM AO_B434B9_WEB_HOOK WHERE REPO_NAME = ? or REPO_NAME is null

2012-12-04 15:15:16,932 WARN [CommitNotifier1 ] com.atlassian.fecru.plugin.commithook.internal.DefaultCommitHookManager DefaultCommitHookManager-collateErrors - Error while processing a commit directive handled by plugin com.atlassian.fecru.plugin.commithook.fecru-jiracommithook-plugin:jiracommithook for changeset a90056a50bb62305ccbd120b7acde3b232eeb499 in repository TestRepo01:

JIRA issue not found: ATP-7

But a review is created in Crucible and assigned to the user named. Since Crucible & Fisheye are on the same codebase/config, this is confusing.

Crucible shows the name of the review as "ATP-7 #comment next try" with ATP-7 a valid link to the issue in Jira. It removed the +review @username.

In Jira there is nothing under comment, but under source:

"ATP-7 #comment next try +review @username" with it all plain text.

In Fisheye it shows:

"ATP-7 #comment next try +review @username" with ATP-7 a valid link to the issue.

Any ideas? Why does Crucible work?

-Kelly

[Kelly Schoenhofen]

The atlassian-jira-security.log file contains the following every 60 seconds:

2012-12-04 12:11:08,767 http-bio-8080-exec-19 anonymous 731x126679x2 1o9z5c9 x.x.x.x /rest/usermanagement/1/user/group/nested login : 'Fisheye' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

2012-12-04 12:11:28,295 http-bio-8080-exec-16 anonymous 731x126686x1 1qx9o19 x.x.x.x /rest/usermanagement/1/authentication login : 'StashVM' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

Those names - Fisheye & StashVM - are the Jira User Server names I used when setting up authentication. However, I can go to both Stash & Fisheye and synchronise users/groups just fine. Why is this logging over and over?