Allow the Jira plugin to post to multiple flows
Currently (at least it seems this way) I can only add one flow key to the Flowdock for Jira configuration on a per-project basis. I want to get a separate business unit using Flowdock but I don't want them in our existing developer flow, thus I can't extend this to them without giving up our own Jira updates.
As it turns out, this is already done, using commas!
Well, here's a pull request:
Would you take pull requests for this one?
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
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
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
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.