Search before asking
Use case
TAPD's latest version introduces a parallel workflow mode, allowing a task(story, bug)'s status to be subdivided into multiple phases that can progress simultaneously. However, when collecting development data from TAPD using DevLake, the story changelog API returns change records for these phases under the status field, but the value field contains either an empty string or a meaningless number. This causes issues in tracking and calculating task(story, bug) status changes accurately.
Description
TAPD's new parallel workflow mode enhances issue tracking by enabling multiple concurrent phases within a single task status. During data collection using DevLake’s TAPD plugin, the story changelog API does include records of these phase changes, but the value field does not provide meaningful data, making it difficult to process and analyze the transitions correctly.
This issue impacts the correctness of workflow tracking and status transition analysis within DevLake. To ensure accurate data collection and processing, we propose modifying the TAPD plugin in DevLake to appropriately handle and extract meaningful values for these status changes.
Expected Improvement:
-
Enhance the TAPD plugin’s data collection and transformation process to correctly support TAPD’s parallel workflow mode.
-
Properly interpret and map status changes from the story changelog API, ensuring the value field is processed accurately.
-
Maintain consistency in task status tracking across all workflow modes within TAPD.
This enhancement will improve the reliability of TAPD data analysis in DevLake, ensuring users can correctly visualize and interpret development progress when using TAPD’s parallel workflows.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
TAPD's latest version introduces a parallel workflow mode, allowing a task(story, bug)'s status to be subdivided into multiple phases that can progress simultaneously. However, when collecting development data from TAPD using DevLake, the story changelog API returns change records for these phases under the status field, but the value field contains either an empty string or a meaningless number. This causes issues in tracking and calculating task(story, bug) status changes accurately.
Description
TAPD's new parallel workflow mode enhances issue tracking by enabling multiple concurrent phases within a single task status. During data collection using DevLake’s TAPD plugin, the story changelog API does include records of these phase changes, but the value field does not provide meaningful data, making it difficult to process and analyze the transitions correctly.
This issue impacts the correctness of workflow tracking and status transition analysis within DevLake. To ensure accurate data collection and processing, we propose modifying the TAPD plugin in DevLake to appropriately handle and extract meaningful values for these status changes.
Expected Improvement:
Enhance the TAPD plugin’s data collection and transformation process to correctly support TAPD’s parallel workflow mode.
Properly interpret and map status changes from the story changelog API, ensuring the value field is processed accurately.
Maintain consistency in task status tracking across all workflow modes within TAPD.
This enhancement will improve the reliability of TAPD data analysis in DevLake, ensuring users can correctly visualize and interpret development progress when using TAPD’s parallel workflows.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct