Would it be reasonable to support managing issue-templates?
I'm not so familiar with graphQL but there appear to be hits for template in both mutation and query of the schema.
Over here, we use issue-templates (with sub-issues) to codify workflows like release process / declare-an-incident.
We place a title and description inside the parent-issue template, and inside n sub-issues. We also make the template's parent and sub-issues have some labels.
It would be particularly convenient also to re-order the sub-issues within the template - at the moment, that isn't possible to do via the admin UI, though, so I don't know if the API make it possible to set / change the ordering of sub-issues.
Funding
You can sponsor this specific effort via a Polar.sh pledge below
We receive the pledge once the issue is completed & verified
pksunkara
commented
1 year ago
Would it be reasonable to support managing issue-templates?
I'm not so familiar with graphQL but there appear to be hits for
templatein both mutation and query of the schema.Over here, we use issue-templates (with sub-issues) to codify workflows like release process / declare-an-incident.
We place a title and description inside the parent-issue template, and inside
nsub-issues. We also make the template's parent and sub-issues have some labels.It would be particularly convenient also to re-order the sub-issues within the template - at the moment, that isn't possible to do via the admin UI, though, so I don't know if the API make it possible to set / change the ordering of sub-issues.
Funding