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

Jira Plugin: Add description field support for create_issue tool #830

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

Originally created by @iwasa-kosui on GitHub (Nov 24, 2025).

Originally assigned to: @hjlarry on GitHub.

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.

Currently, the Jira create_issue tool does not support the description field when creating issues.

Use Case

When creating Jira issues programmatically through Dify, users often need to include detailed descriptions along with the summary. The description field is essential for providing context, acceptance criteria, reproduction steps, or any other relevant information.

Proposed Solution

  1. Add a description parameter to the create_issue tool configuration
  2. Implement Markdown to Atlassian Document Format (ADF) conversion for the description field, since Jira Cloud API requires ADF format for rich text fields
  3. Include the converted description in the issue creation payload

2. Additional context or comments

My reference implementation for the Markdown-to-ADF converter will be available and handles:

  • Headings (H1-H6)
  • Bold and italic text
  • Links
  • Inline code
  • Bullet lists and ordered lists (including nested lists)
  • Paragraphs

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @iwasa-kosui on GitHub (Nov 24, 2025). Originally assigned to: @hjlarry on GitHub. ### 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. Currently, the Jira create_issue tool does not support the description field when creating issues. ### Use Case When creating Jira issues programmatically through Dify, users often need to include detailed descriptions along with the summary. The description field is essential for providing context, acceptance criteria, reproduction steps, or any other relevant information. ### Proposed Solution 1. Add a description parameter to the create_issue tool configuration 2. Implement Markdown to Atlassian Document Format (ADF) conversion for the description field, since Jira Cloud API requires ADF format for rich text fields 3. Include the converted description in the issue creation payload ### 2. Additional context or comments My reference implementation for the Markdown-to-ADF converter will be available and handles: - Headings (H1-H6) - Bold and italic text - Links - Inline code - Bullet lists and ordered lists (including nested lists) - Paragraphs ### 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:39 -05:00
yindo closed this issue 2026-02-16 10:20:39 -05:00
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#830
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?