Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
2 of 3 tasks
Startrekzky opened this issue Jul 9, 2024 · 4 comments
Open
2 of 3 tasks

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

Startrekzky opened this issue Jul 9, 2024 · 4 comments
Assignees
@d4x1
Labels
improvement pr-type/feature-development This PR is to develop a new feature Stale type/feature-request This issue is a proposal for something new
Milestone
v1.1

Comments

@Startrekzky
Copy link
Contributor

Startrekzky commented Jul 9, 2024 •
edited
Loading

Search before asking

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

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?

  • Yes I am willing to submit a PR!

Code of Conduct
@Startrekzky Startrekzky added the type/feature-request This issue is a proposal for something new label Jul 9, 2024
@dosubot dosubot bot added improvement pr-type/feature-development This PR is to develop a new feature labels Jul 9, 2024
@d4x1 d4x1 self-assigned this Jul 9, 2024
@d4x1 d4x1 added this to the v1.1 milestone Jul 9, 2024
This was referenced Jul 9, 2024
Merged
Merged
Merged
Merged
Merged
This was referenced Jul 16, 2024
Merged
Merged
@d4x1
Copy link
Contributor

d4x1 commented Jul 17, 2024 •
edited
Loading

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

d4x1 added a commit that referenced this issue Jul 17, 2024
@d4x1
cherry pick all #7708 related commits to release-v1.0 (#7759)
6b624a9 
* feat(jira): collector account from issue changelog items as much as possible

* fix(jira): fix migration scripts

* feat(jira): add `_tool_jira_issue_fields`, collect account field from the new table

* fix(jira): fix testes

* fix(jira): fix `reporter` field in issue change log items

* fix(jira): fix account id when there is no from/to values

* fix(jira): fix OriginalToValue in issue_changelogs

* fix(jira): don't use `tmpFromAccountId` and `tmpToAccountId` in issue changelogs

* fix(jira): remove all usage of `tmpFromAccountId` and `tmpToAccountId`

* refactor(jira): remove some codes

* fix(jira): fix e2e test

* fix(jira): fix wrong key in `issueFieldMap`
@d4x1 d4x1 mentioned this issue Aug 14, 2024
Merged
4 tasks
@github-actions GitHub Actions
Copy link

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 github-actions bot added the Stale label Sep 16, 2024
@d4x1 d4x1 removed the Stale label Sep 18, 2024
@github-actions GitHub Actions
Copy link

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 github-actions bot added the Stale label Nov 18, 2024
@d4x1 d4x1 removed the Stale label Nov 19, 2024
@klesh klesh mentioned this issue Nov 20, 2024
Merged
@github-actions GitHub Actions
Copy link

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 github-actions bot added the Stale label Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@d4x1 d4x1

Labels
improvement pr-type/feature-development This PR is to develop a new feature Stale type/feature-request This issue is a proposal for something new
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
2 participants
@d4x1 @Startrekzky