Select which changes (status/fields) should be sent as Slack notifications about redmine-slack HOT 3 OPEN

(I wrote #41, which optionally filters out ticket updates entirely. #90 offers the ability to show when a ticket is closed, as it is the natural companion of showing new tickets.)

I can see how this could get out of hand in terms of the various scenarios an end-user may want to update Slack. This particular addition is probably fine, but I can see future cases perhaps coming in conflict.

With #90 added, these scenarios are covered:

• issue is created
• issue is closed

These are not yet covered at a granular level:

• issue status changes
• issue is assignee changes
• issue priority changes
• issue comment is added

These would be on my wishlist, but right now are not exposed in the update anyway:

• issue target version changes
• issue due date changes
• issue start date changes
• issue percent complete changes

I would apply these options as "If any of these conditions are met, post the update. If none are met, ignore it."

from redmine-slack.

@kapod this would be a great feature :) PRs are welcome, but unfortunately I don't have the bandwidth to work on this myself at the moment.

from redmine-slack.

@stephenyeargin good summary. Looks like we'd need a more generic filtering mechanism that can act on the properties of the issue before and after the update. I'd like to avoid a proliferation of options - that would get confusing quickly (post on issue complete, post on status change, etc).

from redmine-slack.