You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, only one rule will match a message, dispatching only one issue. Theoretically this could be increased to allow a single message to match multiple rules, in case a piece of information should be surfaced in multiple locations (e.g. internal and customer-facing documentation).
Also, theoretically, the plugin could support dispatching issues to multiple systems (e.g. GitHub and JIRA).
And, finally, the Config.successReaction value could be overridden per-rule, to ensure that multiple emojis for a single message can result in multiple issues getting filed at different times.
The question is: Is this worth implementing? Would anyone actually use this?
The text was updated successfully, but these errors were encountered:
Right now, only one rule will match a message, dispatching only one issue. Theoretically this could be increased to allow a single message to match multiple rules, in case a piece of information should be surfaced in multiple locations (e.g. internal and customer-facing documentation).
Also, theoretically, the plugin could support dispatching issues to multiple systems (e.g. GitHub and JIRA).
And, finally, the
Config.successReaction
value could be overridden per-rule, to ensure that multiple emojis for a single message can result in multiple issues getting filed at different times.The question is: Is this worth implementing? Would anyone actually use this?
The text was updated successfully, but these errors were encountered: