[Feature][Jira issue changelogs] Add customized jira account fields to table.accounts
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
Use case
As a PM,
-
I used the
original_from_valueandoriginal_to_valueof the field wherefield_name = assigneein theissues.changelogsto measure who has contributed to a Jira issue during the whole lifecycle. -
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
- Other Jira issue fields whose
jira_field_type=jira_accountin tableissue_changelogsshould be written into tableaccounts.- There's a Jira API to judge if a field is
jira_account. tmpFromAccountId/tmpToAccountId
- There's a Jira API to judge if a field is
- Other Jira issue fields whose
jira_field_type=jira_accountin tableissue_changelogsshould be stored in the form ofaccounts.id, notname.
Related issues
No response
Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Just keep this issue open, plugin issue_trace(added in release-v1.0) should be updated.
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.
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.
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.
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.
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.
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.