apache / incubator-devlake

Apache DevLake is an open-source dev data platform to ingest, analyze, and visualize the fragmented data from DevOps tools, extracting insights for engineering excellence, developer experience, and community growth.
https://devlake.apache.org/
Apache License 2.0
2.61k stars 528 forks source link

[Feature][Jira issue changelogs] Add customized jira account fields to table.accounts #7708

Open Startrekzky opened 4 months ago

Startrekzky commented 4 months ago

Search before asking

Use case

As a PM,

  1. I used the original_from_value and original_to_value of the field where field_name = assignee in the issues.changelogs to measure who has contributed to a Jira issue during the whole lifecycle. image

  2. I also use another customized Jira issue field (whose jira_field_type = jira_account), for example, reporter, to manage the contributors of Jira issues. And I want to measure the contribution by Jira issue reporters.

Here comes the problem: When I get the original_from_value and original_to_value of the field where field_name = reporter. The values are reporter's names, not their IDs that I could join the accounts table for full user profile.

Description

To Do

  1. Other Jira issue fields whose jira_field_type = jira_account in table issue_changelogs should be written into table accounts.
    • There's a Jira API to judge if a field is jira_account. tmpFromAccountId/tmpToAccountId
  2. Other Jira issue fields whose jira_field_type = jira_account in table issue_changelogs should be stored in the form of accounts.id, not name.

Related issues

No response

Are you willing to submit a PR?

Code of Conduct

d4x1 commented 4 months ago

Just keep this issue open, plugin issue_trace(added in release-v1.0) should be updated.

github-actions[bot] commented 2 months ago

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] commented 1 week ago

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.