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 as datasource #839

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

Originally created by @matteo-rama on GitHub (Nov 28, 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.

I am trying to fetch a list of jira ticket, that belong to a specific board/project.
i would like to fetch all jira that are in status resolved, and have them as a knowledge base for other ticket, so with another workflow i can use them to get insight on typical question.

What i think i miss is a way to have jira as "datasource" as the plugin don't work as datasource from knowledge base.

Any possible workaround or best approach that i am missing? to be fair i installed dify just yesterday so i could have just doing things with wrong approach

thanks!

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @matteo-rama on GitHub (Nov 28, 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/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. I am trying to fetch a list of jira ticket, that belong to a specific board/project. i would like to fetch all jira that are in status resolved, and have them as a knowledge base for other ticket, so with another workflow i can use them to get insight on typical question. What i think i miss is a way to have jira as "datasource" as the plugin don't work as datasource from knowledge base. Any possible workaround or best approach that i am missing? to be fair i installed dify just yesterday so i could have just doing things with wrong approach thanks! ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the question label 2026-02-16 10:20:40 -05:00
yindo closed this issue 2026-02-16 10:20:40 -05:00
yindo commented 2026-02-16 10:20:40 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @matteo-rama! I'm Dosu and I’m helping the dify team.

Dify does not currently support Jira as a native datasource for knowledge base ingestion. The existing Jira plugin only supports basic authentication and is not designed to work as a datasource for importing Jira tickets into the knowledge base. There are known issues with Personal Access Token (PAT) authentication, but you can try modifying the plugin code to pass the API token to the token parameter instead of password if you want to experiment with plugin-based access [source].

For your use case—using resolved Jira tickets as a knowledge base—the most practical workaround is to export the relevant Jira tickets (for example, as CSV or JSON) and then import them into Dify as local files, which is a supported datasource type. This allows you to leverage Jira data for insights and workflows without direct integration.

If you want a more automated solution, you could develop a custom plugin that wraps the Jira API and registers the necessary provider/datasource declarations, following the extensible architecture used for other datasources in Dify [source].

Let me know if you want step-by-step guidance for exporting/importing Jira tickets or tips for developing a custom plugin!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 28, 2025): <!-- Greeting --> Hi @matteo-rama! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Dify does not currently support Jira as a native datasource for knowledge base ingestion. The existing Jira plugin only supports basic authentication and is not designed to work as a datasource for importing Jira tickets into the knowledge base. There are known issues with Personal Access Token (PAT) authentication, but you can try modifying the plugin code to pass the API token to the `token` parameter instead of `password` if you want to experiment with plugin-based access [[source](https://github.com/langgenius/dify-official-plugins/issues/1379)]. For your use case—using resolved Jira tickets as a knowledge base—the most practical workaround is to export the relevant Jira tickets (for example, as CSV or JSON) and then import them into Dify as local files, which is a supported datasource type. This allows you to leverage Jira data for insights and workflows without direct integration. If you want a more automated solution, you could develop a custom plugin that wraps the Jira API and registers the necessary provider/datasource declarations, following the extensible architecture used for other datasources in Dify [[source](https://github.com/langgenius/dify/blob/ddad2460f3ee4906df6819c48babaeab62221b43/api/core/datasource/datasource_manager.py#L18-L81)]. Let me know if you want step-by-step guidance for exporting/importing Jira tickets or tips for developing a custom plugin! <!-- 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/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/65811acd-adbd-403c-863e-90d87d4068ff?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Dify%20does%20not%20currently%20support%20Jira%20as%20a%20native%20datasource%20for%20knowledge%20base%20ingestion.%20The%20existing%20Jira%20plugin%20only%20supports%20basic%20authentication%20and%20is%20not%20designed%20to%20work%20as%20a%20datasource%20for%20importing%20Jira%20tickets%20into%20the%20knowledge%20base.%20There%20are%20known%20issues%20with%20Personal%20Access%20Token%20%28PAT%29%20authentication%2C%20but%20you%20can%20try%20modifying%20the%20plugin%20code%20to%20pass%20the%20API%20token%20to%20the%20%60token%60%20parameter%20instead%20of%20%60password%60%20if%20you%20want%20to%20experiment%20with%20plugin-based%20access%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1379%29%5D.%0A%0AFor%20your%20use%20case%E2%80%94using%20resolved%20Jira%20tickets%20as%20a%20knowledge%20base%E2%80%94the%20most%20practical%20workaround%20is%20to%20export%20the%20relevant%20Jira%20tickets%20%28for%20example%2C%20as%20CSV%20or%20JSON%29%20and%20then%20import%20them%20into%20Dify%20as%20local%20files%2C%20which%20is%20a%20supported%20datasource%20type.%20This%20allows%20you%20to%20leverage%20Jira%20data%20for%20insights%20and%20workflows%20without%20direct%20integration.%0A%0AIf%20you%20want%20a%20more%20automated%20solution%2C%20you%20could%20develop%20a%20custom%20plugin%20that%20wraps%20the%20Jira%20API%20and%20registers%20the%20necessary%20provider/datasource%20declarations%2C%20following%20the%20extensible%20architecture%20used%20for%20other%20datasources%20in%20Dify%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/ddad2460f3ee4906df6819c48babaeab62221b43/api/core/datasource/datasource_manager.py%23L18-L81%29%5D.%0A%0ALet%20me%20know%20if%20you%20want%20step-by-step%20guidance%20for%20exporting/importing%20Jira%20tickets%20or%20tips%20for%20developing%20a%20custom%20plugin%21)&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/issues/28925)
yindo commented 2026-02-16 10:20:41 -05:00
Author
Owner
Copy Link
Copy Source

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

Jira is not currently supported as a native datasource for knowledge bases in Dify. The existing Jira plugin only handles basic issue creation and does not support fetching tickets or acting as a datasource for the knowledge base. There are also authentication limitations: the plugin only supports Basic login, not Personal Access Tokens (PAT), which can cause authorization errors if you try to use PATs instead of username/password combos (source).

If you want to use Jira tickets as a knowledge base, the most practical workaround right now is to export the relevant Jira issues (for example, all resolved tickets) to a CSV or JSON file and then import that file into Dify as a local file datasource. This lets you leverage Dify's knowledge base features without direct Jira integration.

For a more automated or scalable solution, you would need to develop a custom datasource plugin for Jira. This would involve:

  • Defining Jira-specific credentials and parameters,
  • Implementing the necessary plugin endpoints to fetch and transform Jira data,
  • Registering a new datasource provider type and controller in Dify's plugin architecture.

If you want to explore building a custom plugin, I can provide more technical details or point you to the relevant parts of the codebase that handle datasource plugins and integration. Let me know if you want to go deeper on that!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 29, 2025): <!-- Answer --> Jira is not currently supported as a native datasource for knowledge bases in Dify. The existing Jira plugin only handles basic issue creation and does not support fetching tickets or acting as a datasource for the knowledge base. There are also authentication limitations: the plugin only supports Basic login, not Personal Access Tokens (PAT), which can cause authorization errors if you try to use PATs instead of username/password combos [(source)](https://github.com/langgenius/dify-official-plugins/issues/1379). If you want to use Jira tickets as a knowledge base, the most practical workaround right now is to export the relevant Jira issues (for example, all resolved tickets) to a CSV or JSON file and then import that file into Dify as a local file datasource. This lets you leverage Dify's knowledge base features without direct Jira integration. For a more automated or scalable solution, you would need to develop a custom datasource plugin for Jira. This would involve: - Defining Jira-specific credentials and parameters, - Implementing the necessary plugin endpoints to fetch and transform Jira data, - Registering a new datasource provider type and controller in Dify's plugin architecture. If you want to explore building a custom plugin, I can provide more technical details or point you to the relevant parts of the codebase that handle datasource plugins and integration. Let me know if you want to go deeper on that! <!-- 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/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/24c00ab2-a8a3-4506-b50f-b4f8df57408d?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Jira%20is%20not%20currently%20supported%20as%20a%20native%20datasource%20for%20knowledge%20bases%20in%20Dify.%20The%20existing%20Jira%20plugin%20only%20handles%20basic%20issue%20creation%20and%20does%20not%20support%20fetching%20tickets%20or%20acting%20as%20a%20datasource%20for%20the%20knowledge%20base.%20There%20are%20also%20authentication%20limitations%3A%20the%20plugin%20only%20supports%20Basic%20login%2C%20not%20Personal%20Access%20Tokens%20%28PAT%29%2C%20which%20can%20cause%20authorization%20errors%20if%20you%20try%20to%20use%20PATs%20instead%20of%20username/password%20combos%20%5B%28source%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1379%29.%0A%0AIf%20you%20want%20to%20use%20Jira%20tickets%20as%20a%20knowledge%20base%2C%20the%20most%20practical%20workaround%20right%20now%20is%20to%20export%20the%20relevant%20Jira%20issues%20%28for%20example%2C%20all%20resolved%20tickets%29%20to%20a%20CSV%20or%20JSON%20file%20and%20then%20import%20that%20file%20into%20Dify%20as%20a%20local%20file%20datasource.%20This%20lets%20you%20leverage%20Dify%27s%20knowledge%20base%20features%20without%20direct%20Jira%20integration.%0A%0AFor%20a%20more%20automated%20or%20scalable%20solution%2C%20you%20would%20need%20to%20develop%20a%20custom%20datasource%20plugin%20for%20Jira.%20This%20would%20involve%3A%0A-%20Defining%20Jira-specific%20credentials%20and%20parameters%2C%0A-%20Implementing%20the%20necessary%20plugin%20endpoints%20to%20fetch%20and%20transform%20Jira%20data%2C%0A-%20Registering%20a%20new%20datasource%20provider%20type%20and%20controller%20in%20Dify%27s%20plugin%20architecture.%0A%0AIf%20you%20want%20to%20explore%20building%20a%20custom%20plugin%2C%20I%20can%20provide%20more%20technical%20details%20or%20point%20you%20to%20the%20relevant%20parts%20of%20the%20codebase%20that%20handle%20datasource%20plugins%20and%20integration.%20Let%20me%20know%20if%20you%20want%20to%20go%20deeper%20on%20that%21)&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/2152)
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 question
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#839
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?