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.

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

Add TAPD as our data source #560

Closed
klesh opened this issue Oct 26, 2021 · 4 comments · Fixed by #1434
Closed

Add TAPD as our data source #560

klesh opened this issue Oct 26, 2021 · 4 comments · Fixed by #1434
Assignees
Labels
type/feature-request This issue is a proposal for something new
Milestone

Comments

@klesh
Copy link
Contributor

klesh commented Oct 26, 2021

Description

TAPD is used by many of our customer, it should be supported.

Describe the solution you'd like

Develop a plugin to import data from TAPD

Has the Feature been Requested Before?

Yes

@klesh klesh added the type/feature-request This issue is a proposal for something new label Oct 26, 2021
@warren830 warren830 self-assigned this Apr 21, 2022
@warren830 warren830 mentioned this issue Apr 21, 2022
@Startrekzky Startrekzky added this to the v0.11.0 milestone Apr 21, 2022
@klesh
Copy link
Contributor Author

klesh commented Apr 24, 2022

Can we reach out to some real TaPD users and try to collect their actual data? @Startrekzky

@klesh
Copy link
Contributor Author

klesh commented Apr 24, 2022

@Startrekzky : mock data on our own.

@warren830
Copy link
Contributor

  1. Rate limit problem
    The doc of tapd said the rate limit is 6000req/10min, but when we are using this rate limit to send requests, we got error like below:
    [{"status":429,"data":"","info":"To many requests, api account xxxxxx! max request rates is 1800req/10min"}]

  2. Status mapping problem
    In the tapd platform, we can set one status to be initial status, but we can't get this information(which status is initial) from api request.

@warren830
Copy link
Contributor

  1. Changelog Item problem

    "field": "secret_root_id",
    "field_label": "可访问范围",
    "value_after": {
    "allow_list": "x",
    "secret_root_id": "xxxxx",
    "participant_fields": 1
    },
    "value_before": {
    "allow_list": "",
    "secret_root_id": 0,
    "participant_fields": 0
    },
    "secret_root_id": "xxx",
    "value_after_parsed": {
    "allow_list": "xxxx;xxx",
    "secret_root_id": "xxx",
    "participant_fields": "1"
    },
    "value_before_parsed": {
    "allow_list": "",
    "secret_root_id": "0",
    "participant_fields": "0"
    }
    }
    sometimes the field value_%_parsed is json, sometimes it's a string...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature-request This issue is a proposal for something new
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants