Writing bulk tickets that must be applied to every project before it is completed is horrible for tracking, daily work, etc. This ticket is just to capture my ideas around solving this problem long term as we will continue to service a lot of projects both internally, externally, etc.
Just make a little bash wrapper that allows to be able to write a ticket for a list of projects stored in a file (should be able to leverage hub and lab command line tools).
Be able to specify the file, edit the issue before it is created in each project or before it is created for every project.
Be able to generate an empty bug template.
Be able to register a new project easily.
Be able to use with projects on Gitlab or Github.
Be able to use with private and public projects with services above.
Be able to clone out a pre-existing issue to another project(s) on the fly (using pre-defined groups or on the fly, guard against dupes).
If a target project does not have a label being used, create it for that project (bonus, but maybe consider using git-labels to simply sync everything ahead of time instead of tackling this in the wrapper)
Writing bulk tickets that must be applied to every project before it is completed is horrible for tracking, daily work, etc. This ticket is just to capture my ideas around solving this problem long term as we will continue to service a lot of projects both internally, externally, etc.
Just make a little bash wrapper that allows to be able to write a ticket for a list of projects stored in a file (should be able to leverage
hubandlabcommand line tools). Be able to specify the file, edit the issue before it is created in each project or before it is created for every project. Be able to generate an empty bug template. Be able to register a new project easily. Be able to use with projects on Gitlab or Github. Be able to use with private and public projects with services above. Be able to clone out a pre-existing issue to another project(s) on the fly (using pre-defined groups or on the fly, guard against dupes). If a target project does not have a label being used, create it for that project (bonus, but maybe consider using git-labels to simply sync everything ahead of time instead of tackling this in the wrapper)