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.

Sign up for GitHub

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

Jump to bottom

Dedupe results for get_key_references API #1209

Closed
8 tasks
abitmore opened this issue Jul 30, 2018 · 6 comments
Closed
8 tasks

Dedupe results for get_key_references API #1209

abitmore opened this issue Jul 30, 2018 · 6 comments
Assignees
@oxarbitrage
Labels
1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2d Developing Status indicating currently designing and developing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) api
Milestone
3.2.0 - Feature R...

Comments

@abitmore
Copy link
Member

abitmore commented Jul 30, 2018 •
edited
Loading

get_key_references API now may return duplicate accounts (see #1753 (comment)).

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
    • Assigned:
    • Estimated: TBD
  • Perform QA/Testing
  • Update Documentation
@abitmore abitmore added the api label Jul 30, 2018
@ryanRfox ryanRfox added 1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2a Discussion Needed Prompt for team to discuss at next stand up. 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) labels Jul 31, 2018
@windycrypto
Copy link
Member

Let me do it :D

@ryanRfox
Copy link
Contributor

Assigned to @cifer-lee Estimation is TBD

@ryanRfox
Copy link
Contributor

ryanRfox commented Aug 10, 2018 •
edited
Loading

@abitmore I added this issue to the Community Claims Project Board for my tracking. I also added it to the 201810 Feature Release Project Board and Milestone. Please let me know if this is an appropriate way to notify the Core Team of an active effort? I feel this allows the Core Team visability and the ability to move these ad-hoc Issues out of the <Current Release> and into <Future Release> if they will in fact not be included.

Appreciate your feedback.

@ryanRfox ryanRfox added 2d Developing Status indicating currently designing and developing a solution and removed 2a Discussion Needed Prompt for team to discuss at next stand up. labels Aug 10, 2018
@abitmore
Copy link
Member Author

@cifer-lee any update please?

@pmconrad
Copy link
Contributor

Unassigned due to lack of feedback.

@oxarbitrage oxarbitrage mentioned this issue Jun 13, 2019
Merged
@oxarbitrage oxarbitrage self-assigned this Jun 13, 2019
@oxarbitrage oxarbitrage mentioned this issue Jun 13, 2019
Open
@oxarbitrage
Copy link
Member

Closed by #1795

@pmconrad pmconrad mentioned this issue Jun 20, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oxarbitrage oxarbitrage

Labels
1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2d Developing Status indicating currently designing and developing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) api
Projects
None yet
Milestone
3.2.0 - Feature Release
Development

No branches or pull requests
5 participants
@windycrypto @pmconrad @abitmore @ryanRfox @oxarbitrage