langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Enable the feishu_task tool to support the creation or editing of more detailed parameter settings #773

New Issue
Closed
opened 2026-02-16 10:20:28 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:20:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @lycohana on GitHub (Nov 3, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When using the feishu_task tool, I found that the original task creation action was missing many features I needed, such as setting reminder times or directly assigning task members. Therefore, I would like to enhance its functionality for my future use.

2. Additional context or comments

Image like this.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @lycohana on GitHub (Nov 3, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. When using the feishu_task tool, I found that the original task creation action was missing many features I needed, such as setting reminder times or directly assigning task members. Therefore, I would like to enhance its functionality for my future use. ### 2. Additional context or comments <img width="706" height="947" alt="Image" src="https://github.com/user-attachments/assets/76dccf9b-7289-4413-94e2-a6bb9d6f47fb" /> like this. ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the enhancement label 2026-02-16 10:20:28 -05:00
yindo closed this issue 2026-02-16 10:20:28 -05:00
yindo commented 2026-02-16 10:20:28 -05:00
Author
Owner
Copy Link
Copy Source

@lycohana commented on GitHub (Nov 4, 2025):

I understand why the previous method didn't work; the plugin uses the v1 version of the API, which will be abandoned, and I'm planning to refactor to the v2 version of the API!

@lycohana commented on GitHub (Nov 4, 2025): I understand why the previous method didn't work; the plugin uses the v1 version of the API, which will be abandoned, and I'm planning to refactor to the v2 version of the API!
yindo commented 2026-02-16 10:20:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 4, 2025):

Hi @lycohana! I'm Dosu and I’m helping the dify-official-plugins team.

Great plan! There’s already a merged pull request that migrated the feishu_task plugin to a newer API version, likely v2, and it adds support for more detailed parameters like start time, end time, completed time, and direct member assignment with roles (assignee or follower) in task creation and management. You’ll want to review the updated files—especially create_task.yaml, add_members.yaml, and the new Python scripts in tools/feishu_task/—to see how the new parameters and endpoints are handled. The manifest and provider configs also now require permissions like task:task:write and contact:user.id:readonly for these features. This should give you a solid foundation for your refactor and any further enhancements you want to make. You can check out the details in the migrate feishu task tool PR. If you have questions about specific implementation details or want to discuss further improvements, feel free to ask!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 4, 2025): <!-- Greeting --> Hi @lycohana! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> Great plan! There’s already a merged pull request that migrated the feishu_task plugin to a newer API version, likely v2, and it adds support for more detailed parameters like start time, end time, completed time, and direct member assignment with roles (assignee or follower) in task creation and management. You’ll want to review the updated files—especially `create_task.yaml`, `add_members.yaml`, and the new Python scripts in `tools/feishu_task/`—to see how the new parameters and endpoints are handled. The manifest and provider configs also now require permissions like `task:task:write` and `contact:user.id:readonly` for these features. This should give you a solid foundation for your refactor and any further enhancements you want to make. You can check out the details in the [migrate feishu task tool PR](https://github.com/langgenius/dify-official-plugins/pull/283). If you have questions about specific implementation details or want to discuss further improvements, feel free to ask! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1991)
yindo commented 2026-02-16 10:20:28 -05:00
Author
Owner
Copy Link
Copy Source

@lycohana commented on GitHub (Nov 4, 2025):

Hi @lycohana! I'm Dosu and I’m helping the dify-official-plugins team.

Great plan! There’s already a merged pull request that migrated the feishu_task plugin to a newer API version, likely v2, and it adds support for more detailed parameters like start time, end time, completed time, and direct member assignment with roles (assignee or follower) in task creation and management. You’ll want to review the updated files—especially create_task.yaml, add_members.yaml, and the new Python scripts in tools/feishu_task/—to see how the new parameters and endpoints are handled. The manifest and provider configs also now require permissions like task:task:write and contact:user.id:readonly for these features. This should give you a solid foundation for your refactor and any further enhancements you want to make. You can check out the details in the migrate feishu task tool PR. If you have questions about specific implementation details or want to discuss further improvements, feel free to ask!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

I checked, and actually that PR is using the v1 version of the API, which is too outdated

@lycohana commented on GitHub (Nov 4, 2025): > Hi [@lycohana](https://github.com/lycohana)! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. > > Great plan! There’s already a merged pull request that migrated the feishu_task plugin to a newer API version, likely v2, and it adds support for more detailed parameters like start time, end time, completed time, and direct member assignment with roles (assignee or follower) in task creation and management. You’ll want to review the updated files—especially `create_task.yaml`, `add_members.yaml`, and the new Python scripts in `tools/feishu_task/`—to see how the new parameters and endpoints are handled. The manifest and provider configs also now require permissions like `task:task:write` and `contact:user.id:readonly` for these features. This should give you a solid foundation for your refactor and any further enhancements you want to make. You can check out the details in the [migrate feishu task tool PR](https://github.com/langgenius/dify-official-plugins/pull/283). If you have questions about specific implementation details or want to discuss further improvements, feel free to ask! > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c16c2c8b-63e6-4cc2-ad04-7bf716c8cbc2?feedback_type=other)  [![Join Discord](https://camo.githubusercontent.com/d562c2df5e4567ea41d37f1d91a4da0839d8341037045b103b2da268998de17f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/4649f705e2396d6f328dbc8e800a0509c9c17b3b20253b36706c393df124b93d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1991) I checked, and actually that PR is using the v1 version of the API, which is too outdated
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#773
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?