Candidate: Sync GH issues with ADO

RMI-PACTA / actions

Actions for GitHub workflows

4 stars 0 forks source link

Candidate: Sync GH issues with ADO #17

Closed jdhoffa closed 8 months ago

jdhoffa commented 9 months ago

This should likely be on a voluntary or flagged basis, per repo (e.g. we decide which repos we want to auto-populate ADO tickets).

https://learn.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-167-update#sync-github-issues-to-azure-devops-work-items

https://github.com/marketplace/actions/github-issues-to-azure-devops

https://github.com/danhellem/github-actions-issue-to-work-item

jdhoffa commented 9 months ago

Things to test:

Does it create/ update/ delete the GH issue if the ADO ticket is deleted (and vice-versa) (or does it only work in one direction)

jdhoffa commented 9 months ago

Note: In general, we use ADO tickets way more strictly than GH issues (or seem to be attempting to anyway) Requiring every single GH issue to have acceptance criteria, for example, may not be a good thing as it may add a barrier to people flagging things

jdhoffa commented 9 months ago

@cjyetman:

probably would be useful to make the GH Action only push issues with a certain tag?

cjyetman commented 9 months ago

I have some concerns about this simply creating duplicates of every issue/PR, one in GH and one in ADO, that are not in sync, potentially causing a lot of overhead, though I recognize the potential benefit of getting more visibility of GH issues in ADO.

jdhoffa commented 9 months ago

A comment from @cjyetman in what I think was the wrong issue:

Any idea/suspicion what would happen if I selected numerous issues in a repo at the same time and bulk added the ADO tag to them?! That would be awesome if it worked as expected.

To answer that, yes I tested this and confirm that if you:

Create a handful of new issues with no labels
Go into the Issues tab, and bulk select a large handful and add the tag "ADO" to all of them They get added to ADO: