Open marianunez opened 4 years ago
Hi @hanzei , how is it supposed to function? do we assume re-queue is being clicked on item with past date? don't we need to look for all the possible upcoming meeting dates(∞)?
There are two cases to distinguish. Re-queue is clicked for an item scheduled for
/agenda queue $OLD_ITEM
Does this make things more clear?
Hi @hanzei could you please direct me to docs for it?(how do I execute command from web part of the plugin?)
also, today would be different case, /agenda queue $OLD_ITEM
would add it to today by default if its a meeting day.
My suggestion would that you implement an (REST) API in this plugin can all it directly via HTTP from the client. Inspiration can be taken from https://github.com/mattermost/mattermost-plugin-github/pull/239.
I'm aware that the behavior is different from /agenda queue
for meeting day, but I think it still makes sense as a common use case is to re-queue items after they got dropped in a meeting.
https://github.com/mattermost/mattermost-plugin-agenda/pull/89 can be used as a starting point
The post dot menu should show an option to (re-)queue an item to the next meeting that should update the post hashtag to the next meeting date, or if no hashtag is present add the hashtag to queue this item. This would be helpful in cases an item was not covered in the given meeting and is moved to the upcoming one.
This should show an ephemeral message for feedback that the item was queued successfully.
If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please join our "Developers" community channel.
New contributors please see our Developer's Guide.
JIRA: https://mattermost.atlassian.net/browse/MM-22739