Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Can we fetch issues and their linked issues? #483

Open
hemajv opened this issue Nov 2, 2021 · 7 comments
Open

Can we fetch issues and their linked issues? #483

hemajv opened this issue Nov 2, 2021 · 7 comments
Assignees
Labels
kind/question Categorizes issue or PR as a support question. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@hemajv
Copy link

hemajv commented Nov 2, 2021

We are looking to fetch information related to issues and all other issues linked in them. (Related issue: https://github.com/AICoE/okr/issues/8)

For example, we would like to collect all the issues in the OKR repo and fetch all their linked KR issues and aggregate metrics such as percentage of KRs completed (i.e. percentage of items completed in the acceptance criteria checklist), percentage of OKR completed etc to help generate/automate an OKR report. Is it possible to use the MI scheduler for obtaining this data?

cc @xtuchyna

@hemajv
Copy link
Author

hemajv commented Nov 8, 2021

Some fields we would like to capture for every issue (both the parent OKR issue and its respective linked issues):

  • Issue title
  • Issue description
  • Issue checklist/acceptance criteria
  • Issue labels
  • Issue assignees
  • Issue comments

@xtuchyna

@codificat
Copy link
Member

/kind question
(although this will likely turn into /kind feature I guess)

/assign @xtuchyna
can you help clarify?

/triage needs-information

@sesheta sesheta added kind/question Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it. labels Nov 11, 2021
@hemajv
Copy link
Author

hemajv commented Nov 15, 2021

@xtuchyna do we have any updates on this?

@goern
Copy link
Member

goern commented Jan 14, 2022

ping

@sesheta
Copy link
Member

sesheta commented Apr 14, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 14, 2022
@harshad16
Copy link
Member

/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 18, 2022
@VannTen
Copy link
Member

VannTen commented Aug 30, 2022

The Github Graphql API for issues does not appear to feature a list of linked issues, from what I can see (nor does the IssueComment). It does provide a list of trackedInIssues and trackedIssues, but not merely linked one.

@codificat codificat added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Jan 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/question Categorizes issue or PR as a support question. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Status: 🆕 New
Development

No branches or pull requests

7 participants