7 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Anonymous commented  ·  May 21, 2013 10:29 a.m.  ·  Delete

  As it turns out, this is already done, using commas!

• Anonymous commented  ·  May 14, 2013 12:50 p.m.  ·  Delete

  Well, here's a pull request:

  https://github.com/flowdock/flowdock-jira-plugin/pull/1

• Anonymous commented  ·  May 9, 2013 7:58 a.m.  ·  Delete

  Would you take pull requests for this one?

• Anonymous commented  ·  December 17, 2012 7:34 a.m.  ·  Delete

  This one would definitely be useful for us. We're tightly integrated with our client, but not so tightly that we want them in our flow. But they do really appreciate the JIRA feed.

• Björn Bauer commented  ·  August 23, 2012 4:18 a.m.  ·  Delete

  Hi Otto!

  As far as I get it, this only works for public issues.
  "Notifications will be sent only for public issues. Public issues are issues which have a Permission scheme that gives the 'Browse Projects' permission to 'Anyone'(any non-logged-in users)."

  This won't work for us.
  We would need this to support our workflow.

• Chris Conlin commented  ·  February 23, 2012 8:25 a.m.  ·  Delete

  Thanks, Otto. I think I'll hold off for now since the API based integration shows me things formatted much more nicely

• AdminOtto Hilska (Admin, Flowdock) commented  ·  February 22, 2012 11:52 p.m.  ·  Delete

  Thanks for the idea, Chris. I understand the use case, we just initially wanted to leave this functionality out to make the configuration simpler.

  As a workaround you can send email notifications to the other flow by configuring a Notification Scheme in JIRA admin.