Conversation
There was a problem hiding this comment.
From what I understand, the bulk emoji will result in showing the prompt as there's no special check in RequestResolveEventHandler.
Also, how about adding tickets IDs to an array as soon as someone reacted an request with the bulkEmoji, so we're not iterating the whole internal channel when executing !jira bulk command?
|
Wouldn't that stop the filters from being individual for each person? |
It's still possible to make a
|
|
Where would that be posted? |
This comment has been minimized.
This comment has been minimized.
|
The filter is supposed to extend over any request with the reaction. That confuses me as to how that would work. Plus, wouldn't that only work for one user? |
|
Yeah I just gave it another thought and it's quite difficult to maintain if we put the JQL link directly in the embed. So I guess we still have to go with the I strikethroughed and hid my irrelevant reviews. |
|
I changed the code to make it so a map of users to bulk messages is stored instead of iterating through all of the messages in the channel each time. I also fixed the bulk emoji from triggering the prompt/resolution. |
|
Adding an emoji after '!jira bulk' should now resolve all of the requests in the bulk filter with that emoji |
Co-authored-by: SPGoding <15277496+SPGoding@users.noreply.github.com>
Co-authored-by: SPGoding <15277496+SPGoding@users.noreply.github.com>
|
The feature is working very well, but for some reason it seems to ocassionally miss some of the bulk emoji reactions in the internal channels |
Purpose
Large amounts of requests like adding versions can end up being very tedious to do Individually. With a new reaction and command, the bot will provide a Jira filter will all of the tickets from specific requests in order to use a Bulk Action.
Approach
Workflow:
This works per person, so the filter will only contain tickets from requests you personally reacted to
Future work