[Bug][Devlake Pipeline] jira accounts are not processed when subtasks are enabled

[AleksanderBille]

Search before asking

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

What happened

I want into the .env file and cofigured three jira subtasks related to processing account information.

ENABLE_SUBTASKS_BY_DEFAULT="jira:collectIssueChangelogs:true,jira:extractIssueChangelogs:true,jira:convertIssueChangelogs:false,jira:collectAccounts:true,jira:extractAccounts:true,jira:convertAccounts:true"

But when i run the blueprint none of the subtasks are visible in the JSON conf.

Nor are the subtask present in the logs of the pipeline execution.

What do you expect to happen

That the enabled subtasks would be visible in the JSON conf since according to the docs:

https://devlake.apache.org/docs/GettingStarted/Environment#enable_subtasks_by_default

The subtasks found through the link can be enabled by default through the environment vairable found in the .env file.

How to reproduce

Change .env file to include subtasks related to jira account processing.

ENABLE_SUBTASKS_BY_DEFAULT="jira:collectIssueChangelogs:true,jira:extractIssueChangelogs:true,jira:convertIssueChangelogs:false,jira:collectAccounts:true,jira:extractAccounts:true,jira:convertAccounts:true"

docker-compose up and inspect blueprint JSON conf

Anything else

No response

Version

release-v1.0

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

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

[dosubot[bot]]

Hello @AleksanderBille! I'm Dosu, your friendly bot here to help you with bugs, questions, and contributions while you wait for a human maintainer. Let's get your issue sorted out!

The issue you're experiencing might be due to the Jira subtasks related to account processing not being supported or recognized by Apache DevLake. According to the documentation, the supported Jira subtasks include collectIssueChangelogs, extractIssueChangelogs, and convertIssueChangelogs ^[1][2]. The subtasks you mentioned for account processing (collectAccounts, extractAccounts, convertAccounts) are not listed as supported, which could explain why they are not appearing in the JSON configuration or logs.

To resolve this, you should verify whether these account-related subtasks are indeed supported by checking the latest documentation or configuration files. If they are not supported, you may need to adjust your configuration to only include supported subtasks. Additionally, ensure that you restart the DevLake service after making changes to the .env file to apply the new settings.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.