usharerose opened a new issue, #5525:
URL: https://github.com/apache/incubator-devlake/issues/5525

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   In TAPD's task convertor, when process the `parent_issue_id` which is 
considered to a `story` of the `task`, the function `taskIdGen` is called 
instead of `storyIdGen` 
([ref](https://github.com/apache/incubator-devlake/blob/v0.16.0/backend/plugins/tapd/tasks/task_converter.go#L72)).
   
   Then the identifier of a task's parent issue starts with `tapd:TapdTask` 
instead of `tapd:TapdStory` which is assumed the correct one, so that cannot 
get the parent issue in domain layer.
   
   ### What do you expect to happen
   
   The `parent_issue_id` of a `task` should start with `tapd:TapdStory`.
   
   ### How to reproduce
   
   Collect TAPD data into domain layer, and execute the following query in 
database. There would be always no records for parent issues.
   
   ```
   SELECT
       tbl.issue_id AS issue_id,
       parent_issues.id AS parent_issue_id
   FROM (
       SELECT
           issues.id AS issue_id,
           issues.parent_issue_id AS parent_issue_id
       FROM
           issues AS issues
       WHERE
           issues.id LIKE 'tapd:TapdTask%' AND
           issues.parent_issue_id IS NOT NULL
       LIMIT 10
   ) AS tbl
   INNER JOIN
       issues AS parent_issues
   ON
       tbl.parent_issue_id = parent_issues.id
   ```
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v0.17.0-beta2
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to