[Bug][JIRA] Can't retrieve collectIssuleField with JIRA Cloud

[joshuabezaleel]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I was trying to pull data from JIRA Cloud of my company's. My goal is particularly to fill the incidents table/entity for the DORA metrics.

Got this error instead.

time="2025-12-19 14:26:07" level=error msg=" [pipeline service] [pipeline #15] [task #3620] [collectIssuleField] end api collection error\n\tcaused by: error inserting raw rows into _raw_jira_api_issue_fields (500)"
time="2025-12-19 14:26:07" level=info msg=" [pipeline service] [pipeline #15] [task #3620] subtask collectIssuleField finished in 2331 ms"
time="2025-12-19 14:26:07" level=error msg=" [pipeline service] [pipeline #15] [task #3620] subtask collectIssuleField ended unexpectedly\n\tWraps: (2) Error waiting for async Collector execution\n\tWraps: (3) error inserting raw rows into _raw_jira_api_issue_fields (500)\n\tError types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *errors.errorString"

What do you expect to happen

Table _raw_jira_api_issue_fields, _tool_jira_issues, and incidents to be filled, so later I could observe the DORA dashboard on Grafana of Change Failure Rate and Median Time to Restore Service.

How to reproduce

1. Latest version of v1.0.3-beta8
2. Create connection to JIRA Cloud
3. Scope config for Incidents is Task (which I think is default given by JIRA)
4. Execute the pipeline to Collect Data

Anything else

1. Is there anything that I can do to debug/fix this? Or do I need to use the dbt/customize plugin? I saw that the customize only support issues but not incidents.
2. I already changed the log level of lake to debug instead of info but there doesn't seem to be any additional helping log.
3. I'm attaching the JIRA Scope Config (transformation for Incident) and the corresponding JIRA card (which shows the Task work type) if needed.

4. The ICM itself is actually a JIRA project (I haven't been converting it Board since it needs the Admin to do that). Is it possible that it might be the cause? Since I see previous issues that mentions for JIRA connection it only able to retrieve from Board and not Project.

• [Question][Jira Connector] Is there a way to allow Apache DevLake to connect on Jira Projects instead of a Jira Boards ? #8196 (comment)
• Why are boards instead of jira projects selectable in a jira data scope? #6832

Version

v1.0.3-beta8

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[joshuabezaleel]

Any help or pointer is much appreciated, thank you so much! 🙂
@klesh @petkostas @GoSimplicity

[dosubot]

Hi @joshuabezaleel! I'm Dosu and I’m helping the incubator-devlake team.

This error happens because DevLake’s Jira integration is fundamentally scoped to Boards, not Projects. The collectIssueField step (and all Jira data collection) requires a BoardId—if your Jira project doesn’t have an associated board, the pipeline fails with a 500 error when trying to insert into _raw_jira_api_issue_fields. This is a known limitation and is discussed in detail in this thread.

The only current workaround is to create a Jira Board for your project and use that board as the data scope in DevLake. This lets DevLake collect the necessary issue fields and populate the incidents table for DORA metrics. However, this approach requires manual status-to-column mapping and ongoing maintenance if your Jira configuration changes.

If you’re interested in contributing a fix, supporting project-scoped collection (without requiring a board) would require significant changes to the Jira plugin’s scoping logic. There’s community interest in supporting JQL or project-based scoping, but it’s not implemented yet.

Let me know if you want pointers on where to start in the codebase or have other questions!

To reply, just mention @dosu.

---

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

   

[joshuabezaleel]

I'm not really sure whether that the Board exist or not, because it actually shows the option of Board when adding the Scope Config on Devlake UI

This was what was seen on the JIRA, but I can't seem to access it so I can't really confirm whether the Board does exist or it does not (just a placeholder)

[dosubot]

If you see "ICM board" as an option in DevLake's Scope Config UI, that means DevLake successfully fetched it from Jira using the API token configured in your DevLake Jira connection—not your browser session. So, the board exists in Jira and was accessible to the API token at the time DevLake queried for boards. However, Jira permissions can restrict who can view a board in the web UI, so you might not be able to open it directly if you don't have access, even though DevLake can see it via API.

For DevLake data collection to work, the API token used in your Jira connection must have access to the board. If permissions change or the token loses access, collection will fail. If you're unsure, you can ask your Jira admin to confirm the board's existence and your token's permissions, or check DevLake logs for board-related errors during collection.

In short: if the board appears in DevLake, it's not a placeholder—it was returned by Jira's API. But you may need admin help to get direct access or to troubleshoot permission issues if data collection fails.
Source 1 | Source 2

To reply, just mention @dosu.

---

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

   

[klesh]

Can you connect to the database and see if the table _raw_jira_api_issue_fields exists?