This is an automated email from the ASF dual-hosted git repository.

zky pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 8a1f1d184 add original_project to issues table (#349)
8a1f1d184 is described below

commit 8a1f1d1840d670451e82d24b31269dad44dae720
Author: mindlesscloud <[email protected]>
AuthorDate: Fri Dec 16 20:02:28 2022 +0800

    add original_project to issues table (#349)
    
    * add original_project to issues table
    
    * update the description
---
 docs/DataModels/DevLakeDomainLayerSchema.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/DataModels/DevLakeDomainLayerSchema.md 
b/docs/DataModels/DevLakeDomainLayerSchema.md
index 6afa9b3ce..9a1c138f3 100644
--- a/docs/DataModels/DevLakeDomainLayerSchema.md
+++ b/docs/DataModels/DevLakeDomainLayerSchema.md
@@ -64,7 +64,7 @@ Apache DevLake provides 2 plugins:
 An `issue` is the abstraction of Jira/Github/GitLab/TAPD/... issues.
 
 | **field**                   | **type** | **length** | **description**        
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
              [...]
-| :-------------------------- | :------- | :--------- | 
:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 [...]
+|:----------------------------|:---------|:-----------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 [...]
 | `id`                        | varchar  | 255        | An issue's `id` is 
composed of < plugin >:< Entity >:< PK0 >[:PK1]..." <ul><li>For Github issues, 
a Github issue's id is like "github:GithubIssues:< GithubIssueId >". Eg. 
'github:GithubIssues:1049355647'</li> <li>For Jira issues, a Github repo's id 
is like "jira:JiraIssues:< JiraSourceId >:< JiraIssueId >". Eg. 
'jira:JiraIssues:1:10063'. < JiraSourceId > is used to identify which jira 
source the issue came from, since DevLake users  [...]
 | `issue_key`                 | varchar  | 255        | The key of this issue. 
For example, the key of this Github 
[issue](https://github.com/apache/incubator-devlake/issues/1145) is 1145.       
                                                                                
                                                                                
                                                                                
                                                          [...]
 | `url`                       | varchar  | 255        | The url of the issue. 
It's a web address in most cases.                                               
                                                                                
                                                                                
                                                                                
                                                                                
               [...]
@@ -90,6 +90,7 @@ An `issue` is the abstraction of Jira/Github/GitLab/TAPD/... 
issues.
 | `updated_date`              | datetime | 3          | The last time issue 
gets updated                                                                    
                                                                                
                                                                                
                                                                                
                                                                                
                 [...]
 | `resolution_date`           | datetime | 3          | The time the issue 
changes to 'DONE'.                                                              
                                                                                
                                                                                
                                                                                
                                                                                
                  [...]
 | `lead_time_minutes`         | int      |            | Describes the cycle 
time from issue creation to issue resolution.<ul><li>For issues whose type = 
'REQUIREMENT' and status = 'DONE', lead_time_minutes = resolution_date - 
created_date. The unit is minute.</li><li>For issues whose type != 
'REQUIREMENT' or status != 'DONE', lead_time_minutes is null</li></ul>          
                                                                                
                                        [...]
+| `original_project`          | varchar  | 255        | The name of the 
original project. Transformed from a Jira project's name, a TAPD workspace's 
name, etc.                                                                      
                                                                                
                                                                                
                                                                                
                        [...]
 
 #### issue_labels
 

Reply via email to