-
Notifications
You must be signed in to change notification settings - Fork 525
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.
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
[Feature][Convertor] Add data processing for Issue tracking to compute issue status and assignee history #7542
Closed
3 tasks done
Labels
component/framework
This issue or PR relates to the framework
improvement
pr-type/feature-development
This PR is to develop a new feature
type/feature-request
This issue is a proposal for something new
Comments
narrowizard
added
the
type/feature-request
This issue is a proposal for something new
label
May 30, 2024
dosubot
bot
added
component/framework
This issue or PR relates to the framework
improvement
pr-type/feature-development
This PR is to develop a new feature
labels
May 30, 2024
That sounds great, it should be helpful in many cases. |
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 30, 2024
- produce issue_assignee_history and issue_status_history from issue_changelogs apache#7542
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 30, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 30, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 31, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 31, 2024
- produce issue_assignee_history and issue_status_history from issue_changelogs apache#7542
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 31, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
May 31, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
Jun 3, 2024
- produce issue_assignee_history and issue_status_history from issue_changelogs apache#7542
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
Jun 3, 2024
narrowizard
added a commit
to narrowizard/incubator-devlake
that referenced
this issue
Jun 3, 2024
abeizn
pushed a commit
that referenced
this issue
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/framework
This issue or PR relates to the framework
improvement
pr-type/feature-development
This PR is to develop a new feature
type/feature-request
This issue is a proposal for something new
Search before asking
Use case
The new feature should enable the system to handle data processing tasks within the issue tracking domain. This includes calculating and maintaining records of issue statuses and the history of assignees in the respective tables issue_status_history and issue_assignee_history.
Description
In order to enhance the transaction management capabilities of DevLake, there is a need to introduce a new data processing function. The goal is to develop tasks that can compute and store changes over time for issue statuses and assignee data.
The issue_status_history table will hold records of all status changes for issues, including timestamps and the duration for how long each status was maintained.
The issue_assignee_history table will track the history of assignees for each issue, documenting who was handling each issue at any point in time and for how long.
These tables will be critical for generating insights into the workflow of issues and how they are managed by different assignees over time. It will aid in historical analysis and improve transparency in issue tracking.
Please consider adding these capabilities to enhance the analytical power of DevLake and provide teams with in-depth tracking and metrics regarding issue handling and status transitions.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: